feat: replace env files and presets with dynamic configs

[strophy]

Adds a config command to persist config state across sessions. See #61

Issue being fixed or feature implemented

It is currently necessary to specify which network is being used in every single command. This feature stores the config state on disk and provides a number of interfaces with which to manage the configuration.

What was done?

• Described Config and ConfigCollection classes
• Added ConfigRepostitory and read/write logic on command start/end
• Added basic commands for managing configuration
• Implemented config validation
• Removed dotenv files and pass envs to Docker Compose directly
• Data and config dirs depend on network name
• Getting data from configs if options are missing and storing command results in config

How Has This Been Tested?

Manually

Breaking Changes

When complete, this will change the way each command is issued

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[shumkov]

Good job! 👍