Upgrade go-amqp to v1.3.0

[jeolted]

Upgraded go-amqp dependency to v1.3.0. The changes since v1.0.1 are mostly
added features.

Fixed some tests that were failing. The end to end tests still fails on
DeviceToCloud tests. This has been failing for a long time already.

[jeolted]

I ran all the tests and everything passes except the end to end tests for device to cloud: TestEnd2End/mqtt/x509/DeviceToCloud
TestEnd2End/mqtt/sas/DeviceToCloud
TestEnd2End/mqtt-ws/x509/DeviceToCloud
TestEnd2End/mqtt-ws/sas/DeviceToCloud

These tests has been failing since at least version v0.7.0.

I could receive D2C events in iotservice if using the eventhub instead of relying on the redirect from the iothub.

Works:
go run cmd/iothub-service/main.go watch-events -ehcs $EVENTHUB_CONNECTION_STRING

Doesn't work:
go run cmd/iothub-service/main.go watch-events

[jeolted]

I have investigated the errors in the test cases mentioned above and found that the error lies in IoT Hubs implementation (Azure/go-amqp#358).
With a temporary workaround in go-amqp I could get all the tests to pass.

$ go test -count=1 ./...
? github.com/amenzhinsky/iothub/cmd/iothub-device [no test files]
? github.com/amenzhinsky/iothub/cmd/iothub-service [no test files]
? github.com/amenzhinsky/iothub/iotdevice/iotdevicetest [no test files]
? github.com/amenzhinsky/iothub/iotdevice/transport [no test files]
ok github.com/amenzhinsky/iothub/cmd/internal 0.477s
ok github.com/amenzhinsky/iothub/common 1.256s
ok github.com/amenzhinsky/iothub/eventhub 2.365s
ok github.com/amenzhinsky/iothub/iotdevice 4.029s
ok github.com/amenzhinsky/iothub/iotdevice/transport/http 9.952s
ok github.com/amenzhinsky/iothub/iotdevice/transport/mqtt 2.797s
ok github.com/amenzhinsky/iothub/iotservice 20.579s
ok github.com/amenzhinsky/iothub/logger 2.443s
ok github.com/amenzhinsky/iothub/tests 38.116s

@amenzhinsky, would it be possible to approve the workflow?