feat(zkstack): Move containers, explorer and portal commands into ecosystem command

docs/guides/advanced/01_initialization.md

@@ -19,10 +19,10 @@ re-running any `zkstack` command.
 
 #### Containers
 
-The first step to initialize a ZK Stack ecosystem is to run the command `zkstack containers`. This command gets the
-docker images for `postgres` and `reth`. If the `--observability` option is passed to the command, or the corresponding
-option is selected in the interactive prompt, then Prometheus, Grafana and other observability-related images are
-downloaded and run.
+The first step to initialize a ZK Stack ecosystem is to run the command `zkstack ecosystem containers`. This command
+gets the docker images for `postgres` and `reth`. If the `--observability` option is passed to the command, or the
+corresponding option is selected in the interactive prompt, then Prometheus, Grafana and other observability-related
+images are downloaded and run.
 
 Reth (one of the Ethereum clients) will be used to setup our own copy of L1 chain (that our local ZKsync would use).
 

docs/guides/development.md

@@ -50,7 +50,7 @@ The project root directory includes configuration files for an ecosystem with a
 ecosystem, first start the required containers:
 
 ```bash
-zkstack containers
+zkstack ecosystem containers
 ```
 
 Next, run:
@@ -79,7 +79,7 @@ zkstack dev clean all
 You can then reinitialize the ecosystem as described in the [Configure Ecosystem](#configure-ecosystem) section.
 
 ```bash
-zkstack containers
+zkstack ecosystem containers
 zkstack ecosystem init
 ```
 

docs/guides/launch.md

@@ -13,7 +13,7 @@ Prepare dev environment prerequisites: see
 Run the required containers with:
 
 ```bash
-zkstack containers
+zkstack ecosystem containers
 ```
 
 Setup:
@@ -33,7 +33,7 @@ To completely reset the dev environment:
 - Repeat the setup procedure above
 
   ```bash
-  zkstack containers
+  zkstack ecosystem containers
   zkstack ecosystem init
   ```
 
@@ -43,7 +43,7 @@ If you want to run [Dockprom](https://github.com/stefanprodan/dockprom/) stack (
 containers - add `--observability` parameter during initialisation.
 
 ```bash
-zkstack containers --observability
+zkstack ecosystem containers --observability
 ```
 
 or select `yes` when prompted during the interactive execution of the command.
@@ -198,5 +198,5 @@ It appears that no containers are currently running, which is likely the reason
 Ensure that the necessary containers have been started and are functioning correctly to resolve the issue.
 
 ```bash
-zkstack containers
+zkstack ecosystem containers
 ```

zkstack_cli/README.md

@@ -69,7 +69,7 @@ zkstack ecosystem create
 If you choose not to start database & L1 containers after creating the ecosystem, you can later run:
 
 ```bash
-zkstack containers
+zkstack ecosystem containers
 ```
 
 Execute subsequent commands from within the created ecosystem folder:
@@ -133,7 +133,7 @@ zkstack ecosystem init --observability
 To start observability containers:
 
 ```bash
-zkstack containers --observability
+zkstack ecosystem containers --observability
 ```
 
 ### ZK Chain
@@ -259,7 +259,7 @@ Once you have at least one chain initialized, you can run the [portal](https://g
 web-app to bridge tokens between L1 and L2 and more:
 
 ```bash
-zkstack portal
+zkstack ecosystem portal
 ```
 
 This command will start the dockerized portal app using configuration from `apps/portal.config.json` file inside your
@@ -275,7 +275,7 @@ contracts and more.
 First, each chain should be initialized:
 
 ```bash
-zkstack explorer init
+zkstack ecosystem explorer init
 ```
 
 This command creates a database to store explorer data and generatesdocker compose file with explorer services
@@ -284,7 +284,7 @@ This command creates a database to store explorer data and generatesdocker compo
 Next, for each chain you want to have an explorer, you need to start its backend services:
 
 ```bash
-zkstack explorer backend --chain <chain_name>
+zkstack ecosystem explorer backend --chain <chain_name>
 ```
 
 This command uses previously created docker compose file to start the services (api, data fetcher, worker) required for
@@ -293,7 +293,7 @@ the explorer.
 Finally, you can run the explorer app:
 
 ```bash
-zkstack explorer run
+zkstack ecosystem explorer run
 ```
 
 This command will start the dockerized explorer app using configuration from `apps/explorer.config.json` file inside