Unsubscribe from connection loss events when closing service client AMQP connection

[timtay-microsoft]

There is no reason to notify users that the connection was lost when they are actively trying to close the connection.

I also made the other callbacks in these AMQP using clients work asynchronously just like #3224 did for the file upload notification processor callbacks.

[drwill-ms]

You'll need to update the E2E test that I added to ensure the error processor gets called. I'd suggest changing it to ensuring it does NOT get called after a call to CloseAsync, and consider adding another test to ensure it does get called, maybe if the user code throws in the FileUploadNotificationProcessor callback?

[timtay-microsoft]

You'll need to update the E2E test that I added to ensure the error processor gets called. I'd suggest changing it to ensuring it does NOT get called after a call to CloseAsync, and consider adding another test to ensure it does get called, maybe if the user code throws in the FileUploadNotificationProcessor callback?

Sure, I'll do that, too. I'm also working on a proper "reconnection" sample for these AMQP service clients.

Edit: I'll save the sample for another PR to keep this one focused.

[timtay-microsoft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[timtay-microsoft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[timtay-microsoft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).