Note: the discussion here concerns quota enforcement for top-level role, setting quota on sublevel role is not supported.
If a subrole directly makes a reservation, the accounting of `roleConsumedQuota` will be off:
Specifically, in this formula:
`Consumed Quota = reservations + allocation - allocated reservations`
The `reservations` part does not account subrole's reservation to its ancestors. If a reservation is made directly for role "a/b", its reservation is accounted only for "a/b" but not for "a". Similarly, if a top role ( "a") reservation is refined to a subrole ("a/b"), the current code first subtracts the reservation from "a" and then track that under "a/b".
We should make it hierarchical-aware.
The "allocation" and "allocated reservations" are both tracked in the sorter where the hierarchical relationship is considered – allocations are added hierarchically.