AzureServiceBus Transport is failing to receive a message if the endpoint name and topic name are the same but with different casing

[NChaganlal]

Describe the suggested improvement

Is your improvement related to a problem? Please describe.

If endpoint name and topic name are the same but with different casing in Linux, the transport blows up with this exception:

Exception: Azure.Messaging.ServiceBus.ServiceBusException: The messaging entity ‘asb-xxx:Topic:my-topic-name|amqps://asb-xxx.servicebus.windows.net/-cca565ad;9:14:59:source(address:/MyNamespace,filter:)’ could not be found.

Describe the suggested solution

Provide a more meaningful error to the user

Describe alternatives you've considered

Have different names

Additional Context

This improvement originated in this context:
https://discuss.particular.net/t/azure-service-bus-failed-to-receive-error/3951

This is happening in Linux