chore: update deployment workflows and add ECS action

[marcoieni]

Update the deployment workflows by using latest best practices:

• Use GitHub OIDC vs aws_secret_access_key (after this PR is merged, we can delete the AWS secrets from the GitHub Actions secrets)
• Use official docker github actions, which we noticed are more robust in github actions wrt just running docker build
• Introduce caching to take advantage of cargo chef in CI

Based on https://github.com/rust-lang/bors/blob/main/.github/actions/deploy-ecs/action.yml

GitHub OIDC support was added in rust-lang/simpleinfra#1006

Since the docker containers are not used yet, it is safe to merge this PR and experiment with it 👍

Note on the github action

In the previous approach you were using a github action managed by the infra team, while now you don't anymore.

If there's a preference from various teams that the infra team creates a new shared github action (or update the existing one) we'll do it. But for now I would prefer to start with a local github action, so that we can iterate faster.

Other Docker images

Do we need to upload other images to ECR? If yes, we can do it in another PR.

[GuillaumeGomez]

Looks good to me, thanks! Let's wait for @syphar to check as well before merging.

[syphar]

as a first version to play around totally fine.

things for later:

• deploy a specific branch to the staging cluster for testing
• build/deploy the watcher, builder
• run a "release" script / task after deploy (database migrations etc)

View changes since this review