Prevent hierarchical roles from being allocated resources from non-HIERARCHICAL_ROLE agents.

Since non-HIERARCHICAL_ROLE agents cannot handle volume creation on hierarchical roles.

There are a couple of approaches we could have taken here.
(1) Fine-grained: Offer the resources, and reject requests to create volumes on a hierarchical role.
(2) Coarse-grained: Don't offer the resources, require that the agent be upgraded before used with a HIERARCHICAL_ROLE framework.

The current plan is to pursue (2). A couple of reasons for this. First is that this is a generic behavior that can be expected for any new capability. For example, a MULTI_ROLE framework does not get offered resources from a non-MULTI_ROLE agent.

Another reason is there is no feedback loop for a framework when operations fail currently. I believe that it would be more difficult to debug a situation in which a framework's request is being silently dropped, as opposed to not getting offered resources from the agent to begin with.