durable subscriptions: standard-controller

The usage check for the standard-controller should work without
alteration.

The quota check and provisioning will need some modification.

First, the topic associated with the address needs to be looked up. If
the topic cannot be found the address phase should be set to failed
and an error message added.

If the topic associated with the subscription is on the pooled
brokers, then the subscription must be allocated to that same
broker. The quota check in this case should check that there is
sufficient resource still available on that broker. If there is not
then an appropriate error message should be added to the status. (It
may be advisable to process subscription type addresses before other
pending addresses, since they may be tied to a particular broker and
cannot be placed based greatest available capacity).

If the topic associated with the subscription is a sharded topic, then
the subscription should be allocated to which ever of the brokers in
that deployment has the most remaining capacity. If there is
insufficient capacity on any of the existing brokers, the deployment
should be scaled up if possible and the address allocated to the new
instance, or an appropriate error message added to the status if the
address space has insufficient capacity for another broker.

Deprovisioning should work without modification.

The status check for a subscription address should verify that the
single link route is active on the router network.