[DEVEX-108] Add optional parameter to PR infra workflow

[Krusty93]

Update infra_plan.yaml workflow template by adding an optional parameter to override the path where execute the code review.

It was previously hardcoded to infra/resources, but that path is not applicable to few repositories such as io-infra. For this reason, this PR adds an optional parameter tf_configuration_path to allow clients to set the path to the desired location

[gunzip]

lgtm, just note that some projects use multiple cloud providers, ie. "firma con io" which uses azure and aws https://github.com/pagopa/io-sign/tree/main/aws

[Krusty93]

lgtm, just note that some projects use multiple cloud providers, ie. "firma con io" which uses azure and aws pagopa/io-sign@main/aws

Me and @balanza are aware of it and we will do required changes when needed. Probably we only need to authenticate in it

[balanza]

lgtm, just note that some projects use multiple cloud providers, ie. "firma con io" which uses azure and aws pagopa/io-sign@main/aws

Me and @balanza are aware of it and we will do required changes when needed. Probably we only need to authenticate in it

Should we think about a structure like <env>/<csp>/<region>?

[github-actions]

Terraform Plan ('infra/resources/prod/westeurope') 📖

Terraform Plan

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

[Krusty93]

lgtm, just note that some projects use multiple cloud providers, ie. "firma con io" which uses azure and aws pagopa/io-sign@main/aws

Me and @balanza are aware of it and we will do required changes when needed. Probably we only need to authenticate in it

Should we think about a structure like <env>/<csp>/<region>?

I'm not sure since you can have a single TF config with multiple CSPs in it