[AMQP Python] test sending non-closing detach to service (SB) to ensure correct behavior about azure-sdk-for-python HOT 1 OPEN

Additionally, I believe if the link can be closed with close=False both ways in the scenario as follows --

A session endpoint can choose to unmap its output handle for a link. In this case, the endpoint MUST send a [detach](http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-detach) frame to inform the remote peer that the handle is no longer attached to the link endpoint. If both endpoints do this, the link MAY return to a fully detached state. Note that in this case the link endpoints MAY still indirectly communicate via the session, as there could still be active deliveries on the link referenced via delivery-id.

We currently handle a case where we get an incoming non-closing detach from the service -- we should also investigate if that logic works as expected.

Note that one peer MAY send a closing detach while its partner is sending a non-closing detach. In this case, the partner MUST signal that it has closed the link by reattaching and then sending a closing detach.

from azure-sdk-for-python.