Updating CI integration testing

[tegefaulkes]

Description

This PR addresses the changes needed for automated CI integration testing.

Issues Fixed

• Fixes Remove deployment triggering from CI job #90

Tasks

• 1. Verify the lambda is triggering the deployment properly.
• 2. Remove the part of the CI job integration:deployment that triggers the tasks restarting.
• 4. The wait-for-deployment.js needs to be parameterised to work with the testnet and mainnet.
• 5. The integration tests need to be parameterised to work with the testnet and mainnet.
• 6. The wait-for-deployment.js script needs to take into account the CLI version on top of the library version.
• 7. we need to add a wait-for-deployment ci job for the mainnet stage.
• 8. We need add integration tests ci job for the mainnet stage.

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[ghost]

👇 Click on the image for a new way to code review

Legend

[tegefaulkes]

For now I'm only going to add the docker integration tests to the release stage. It's the only integration test that even attempts connections to the network.

[tegefaulkes]

Mostly done, just blocked by the CLI version being available on the https://testnet.polykey.com/api/seednodes/status endpoint and modifying the wait-for-deploy.js script.

[tegefaulkes]

This is pretty much done now but I can't fully test it without some release versions in the staging branch. So the next step is testing in staging with some test release versions.

[tegefaulkes]

Ready to merge now.

[CMCDragonkai]

Make sure to start testing, and @amydevs we need that table on #599 up so we can see that's it working end to end.