Test action against running Octopus Server

[geofflamrock]

There are currently some tests that run on build that exercise the action against a mocked Octopus Server. These are helpful as they run quickly and can provide an indicator if something is wrong with the code. However these run on the code before it is compiled into the final javascript for the action, and don't run against a real Octopus Server so cannot give us the full confidence that a change won't break something for end users of the action.

This PR adds a new job to the build pipeline that uses the compiled action javascript (from the dist folder) against a real Octopus Server installation that is spun up for the job using docker compose. It performs a login using both API keys and OIDC and does a simple query using the octopus cli against the Server to ensure that the action works as expected.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a0b7769

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[geofflamrock]

I'll need to adjust the branch protections to require integration tests job as well as this job

[mattocto]

I've looked this over, and at a high level, it seems fine. If there's something specific you actually wanted reviewed in detail then please find an extra reviewer for it :)