Remove default config in favor of project-/scenario-specific configs; refactor config checks to root command #1355
Description
This issue is related to #1339.
Proposal
- Remove the default config file from Dev Proxy. Instead, users should define custom configuration files tailored to their specific project or scenario.
- With Dev Proxy supporting multiple subcommands, each subcommand should function correctly without relying on a default config.
- The logic for checking whether URLs to watch and plugins are configured should be moved from the subcommands to the root command, where these checks are relevant.
Benefits
- Reduces confusion by making config explicit for each use case.
- Improves clarity and separation of concerns between subcommands and the root command.
- Makes Dev Proxy more flexible and easier to adapt for different scenarios.
Tasks
- Remove support for loading a default config file.
- Update subcommands to work without assuming the presence of a default config.
- Move config checks (URLs, plugins) to the root command logic.
- Update documentation to reflect these changes.
Related to #1339.