Add integration test workflow

[astaticvoid]

Issue #, if available:
#69

Description of changes:
Run integration test for push and pull requests. Uses repo environment secrets to setup AWS credentials.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[astaticvoid]

It appears the integration test is not useful for pull requests since the environment secrets will not be available if PR is from forked repo, even if the deployment is approved by us.
We can use it on push, which gives us confidence before releasing at least. Also provision to run locally gives us some mostly automated assurances before creating the PR.

[bendu]

We could use the github actions OIDC provider instead, so we don't have to remember to rotate the creds.

See https://github.com/aws-actions/configure-aws-credentials#assuming-a-role and https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services

[astaticvoid]

Thanks, we should do that.
It was my original intent, but I hit some policy snags setting up our testing account. Let me take another crack at it for the next revision.

[runakash]

It appears the integration test is not useful for pull requests since the environment secrets will not be available if PR is from forked repo, even if the deployment is approved by us.

How about we run this periodically just for the main branch?

[bendu]

It appears the integration test is not useful for pull requests since the environment secrets will not be available if PR is from forked repo, even if the deployment is approved by us.

How about we run this periodically just for the main branch?

I'm good with either periodic or just on push.