feat: terraform configuration

[itegulov]

Relates to #147

Adds and e2e terraform configuration that:

1. Creates secrets in Secret Manager and populates them with values from the provided variables
2. Builds a docker image and pushes it to an Artifact Registry repository
3. Creates a dedicated service account with the minimum amount of roles needed to run our services
4. Creates N signer nodes (depends on how many secret keys you provide in the variables) + leader node as Cloud Run services

I used this PR to create a testnet environment in pagoda-discovery-platform-prod from scratch. See https://console.cloud.google.com/run/detail/us-east1/mpc-recovery-leader-testnet/metrics?project=pagoda-discovery-platform-prod.

I propose we host mainnet and testnet in pagoda-discovery-platform-prod, while pagoda-discovery-platform-dev will be used exclusively for our internal dev environments (something long-lived for the develop branch and short-lived environments for PRs).

[volovyks]

LGTM
Creates secrets in Secret Manager and populates them with values from the provided variables - any change it can override current setup? Especially what is stored in secret manager.

Creates N signer nodes (depends on how many secret keys you provide in the variables) + leader node as Cloud Run services - so, it's possible to specify, that we want to have 1 signing node + 2 signing nodes managed by other parties in config?

I propose we host mainnet and testnet in pagoda-discovery-platform-prod, while pagoda-discovery-platform-dev will be used exclusively for our internal dev environments (something long-lived for the develop branch and short-lived environments for PRs). - I agree, that short lived dev env should be separated completely. Not strong opinion on testnet + mainnet in one env. If it's a small effort, we can create a separate one for testnet.

[itegulov]

any change it can override current setup? Especially what is stored in secret manager.

Secrets are versioned and I don't think you can delete old revisions, just add new ones

so, it's possible to specify, that we want to have 1 signing node + 2 signing nodes managed by other parties in config?

Yep

Not strong opinion on testnet + mainnet in one env. If it's a small effort, we can create a separate one for testnet.

The reason I am advocating for this is that everyone else (relayer, discovery etc) are hosting testnet services in the *-prod env, so I think we should follow suit

[volovyks]

@itegulov ok, I agree with your reasoning.