Contracts deployment script should allow to specify the environment

[fbac]

We'll be deploying contracts in multiple chains.
Currently, the folders inside config are separated by chain, but an environment (i.e testnet) can be composed by contracts in multiple chains.

Instead of the actual approach, modify forge scripts to allow for grouping or similar solutions:

environment
 |- chain1
 |   |- contractA.json
 |   |_ contractB.json
 |_ chain2
     |- contractC.json
     |_ contractD.json

[neekolas]

@fbac this is done, right?

[fbac]

@fbac this is done, right?

Not yet. Right now we generate the config json files and group them based on the chainId they were deployed to. The first problem is that when deploying contracts for testnet-playground or testnet will override the other env, as they both share the same chainId.

The second problem is our deployments will be multichain so I'd want the deployer to specify the environment to deploy, and generate the config in its folder.