Infra Pipeline: Modular Environment Setups

[namesty]

Overview

This PR aims to enable the new infra CLI command. This command would be used to provide a better, modular and extensible environment orchestration leveraging docker-compose. It also introduces the new infra manifest extension.

The user would declare modules, which are packages that expose a docker-compose YAML file. The CLI would fetch these packages, cache them, resolve the docker-compose YAML of each, and bundle them into a single docker-compose project.

Additionally, the user can write a custom docker-compose file and declare additional services or custom functionality in case no modules suffice their needs. This custom docker-compose is declared and gets bundled and orchestrated along with the rest of the modules.

The CLI also provides some "preset" (or default) environments; which are already properly configured for typical/common use cases. If the user wishes to use one of these, his project's infra manifest gets ignored, and the preset's environment's gets used instead.

The infra command has the following subcommands:

• up: takes all modules and performs a docker-compose up
• down: same as docker-compose down
• config: takes all modules, performs the bundling and outputs the bundled docker-compose project. Useful for validation and debugging.
• vars: prints a list of all required environment variables needed across all bundled modules

And the following flags:

• --modules: acts as a filter of modules. Instead of bundling all modules declared in the infra manifest, it only bundles those specified in the flag.
• --preset: ignores project's infra manifest and uses the selected preset's configuration.

Additional changes

• Given the modular, extensible capability of the infra pipeline, a preset was created to replace the current "test environment". It orchestrates ganache + ens + ipfs, and provides deterministically consistent and permanent ENS contract addresses. The ENS redeployment endpoint was removed from the DevServer. This package is maintained here.
• Leveraging the previous point, a new deployer package was created to assume and use the previous preset environment. No need to specify the ENS registry address in the deploy manifest when deploying on local testnet anymore.