Rebus.AzureServiceBus.RebusPerQueueTopic 6.3.2

Rebus.AzureServiceBus rewrite enabling us following:
           1- Minimal usage for topic/queues even in one-way/two-way communication between Rebus/Masstransit libraries
           2- Skipped implementation of Sagas, this library is working statelessly.
           3- Each topic/queue subscription is living on its own Rebus instance
           4- Health checking of each topic/queue subscription
           5- Full control on Queue/Topic/Topic Subscription naming
           6- For development environment you have an option of: you can prefix all queue/topic names starting with the machine name; this enables me to seperate my queues and application from another guy working on the same project since my queues are created like "oguzhan/queue1" whereas the other guy's "otherguy/queue1"
           7- For topic subscribing, you have the option of whether you will need multiple node subscription or not. If enabled, for topic "Topic1" and subscription name of "sub", it will create "Topic1/sub-node1" whereas "node1" is the docker container name.
           8- In masstransit you have the limitation of each message is transported with its full namespace. If you move its namespace or change class name, MT will not consume the message. This was an annoying issue for all of us in the company. We are free from this issue thanks to Rebus.
           9- Brotli compression of transport message body, so expanding default 256kb limitation of Azure Servicebus to many more.