[ci] Test infrastructure deployment to AWS

[barroco]

PR #974 was reverted since the pull_request trigger started from a public fork is not allowed to get write permissions on the token_id (used to retrieve AWS credentials). This is possible to overcome that limitation by using a pull_request_target trigger. However, we want to make sure that the workflow is triggered only after being reviewed by a commiter, this PR changes the workflow to be triggered manually only. Once merged to master, it will be possible to trigger the workflow on specific branches.

--- Original #974 description
This PR adds a deployment scenario (aws-1) to the repository which sets up a Kubernetes cluster in AWS using a user with limited permissions on the aws account. For the moment, the scenario only setup the Kubernetes infrastructure and tears it down. A Github Actions workflow is configured to run it on pull requests or manually.

This PR will be followed by two others to keep the changeset as small as possible:

1. Deployment of the DSS using helm.
2. Test the deployment of the DSS using interuss/monitoring.

Details of the changes:

• Add new operations deployment utilities in /deploy/operations to create and destroy the Kubernetes cluster.
• terraform-aws-kubernetes
  • Add aws_iam_permissions_boundary variable
  • Add iam_role_node_group_arn output
  • Retrieve token using terraform instead of CLI command
  • Various structure improvements
• Configure the new dss-deploy github workflow

[barroco]

For reference, successful run: https://github.com/interuss/dss/actions/runs/7260181149/job/19778826169