chore: initial integration test

[astromechza]

This PR adds a basic, but high coverage, integration test to the CI pipeline to validate that we can connect, publish, consume, and close cleanly.

The same test setup and prepare functions could be used in more test suites going forward.

[astromechza]

rebased on main

[wagslane]

This looks really good! Thanks for the contribution. Only nit before merging:

    logger.go:58: gorabbit WARN: failed to connect to amqp server ***localhost:5672/: Exception (501) Reason: "read tcp [::1]:34238->[::1]:5672: read: connection reset by peer"
    integration_test.go:52: failed to connect Exception (501) Reason: "read tcp [::1]:34238->[::1]:5672: read: connection reset by peer"
    integration_test.go:49: attempting connection
    logger.go:58: gorabbit WARN: failed to connect to amqp server ***localhost:5672/: Exception (501) Reason: "read tcp [::1]:34250->[::1]:5672: read: connection reset by peer"
    integration_test.go:52: failed to connect Exception (501) Reason: "read tcp [::1]:34250->[::1]:5672: read: connection reset by peer"
    integration_test.go:49: attempting connection
    logger.go:58: gorabbit WARN: failed to connect to amqp server ***localhost:5672/: Exception (501) Reason: "read tcp [::1]:34260->[::1]:5672: read: connection reset by peer"
    integration_test.go:52: failed to connect Exception (501) Reason: "read tcp [::1]:34260->[::1]:5672: read: connection reset by peer"
    integration_test.go:49: attempting connection
    logger.go:58: gorabbit WARN: failed to connect to amqp server ***localhost:5672/: Exception (501) Reason: "read tcp [::1]:34272->[::1]:5672: read: connection reset by peer"
    integration_test.go:52: failed to connect Exception (501) Reason: "read tcp [::1]:34272->[::1]:5672: read: connection reset by peer"
    integration_test.go:49: attempting connection
    logger.go:58: gorabbit WARN: failed to connect to amqp server ***localhost:5672/: Exception (501) Reason: "read tcp [::1]:34280->[::1]:5672: read: connection reset by peer"
    ```
    
    I don't love having all these error-looking logs in the happy path. Can we have it just print a "waiting" message or something and only print the error if it times out completely?

[astromechza]

@wagslane ok it looks a bit more sensible now

(Unfortunately due to a ci issue I had to bump the go version too in this PR)