[proton-j] the transport still emits AMQP header and frames after SASL failure

After the SASL outcome is determined to be failed, the transport still emits the AMQP header and any frames it can such as Open+Close frames.

Most if not all of the code that I have seen creates and opens a Connection object locally at the same time as initiating the SASL exchange. If the SASL outcome is a failure, shared error handling might also lead to the Connection object being closed. In this case I wouldnt expect the transport to emit anything further, but it does currently emit the AMQP header, and open + close frames.