feat(zk_toolbox): Add block explorer support to zk_toolbox

[sanekmelnikov]

What ❔

New zk_inception explorer command for easy block explorer setup.

Usage:

zk_inception explorer init - initializes explorer database and creates config files (executed for all chains, unless --chain is passed)
zk_inception explorer backend - runs backend services (api, data_fetcher, worker) required for block explorer app for a single chain (uses default chain, unless --chain is passed)
zk_inception explorer run - runs block-explorer-app (displays all chains, unless --chain is passed)

Config structure:

• Ecosystem level apps configs:

  • ecosystem/configs/apps.yaml - ecosystem-level configuration for apps, edit that if you want to customize the port for portal and explorer apps.
  • ecosystem/configs/apps/portal.config.json - ecosystem-level configuration for portal app, edit that if you want to customize display names, tokens list, URLs, etc. for any chain for portal. Refer to the format and documentation from the dapp-portal repository.
  • ecosystem/configs/apps/explorer.config.json - ecosystem-level configuration for explorer app, edit that if you want to customize display names, URLs, etc. for any chain for explorer. Refer to the format from block-explorer repository.
  • ecosystem/configs/.generated/explorer.config.js - this file is auto-generated on every explorer run and injected as a runtime config to block-explorer-app docker image for run.
  • ecosystem/configs/.generated/portal.config.js - this file is auto-generated on every portal run and injected as a runtime config to dapp-portal docker image for run.

• Chain level apps configs:

  • chain/configs/explorer-docker-compose.yml - configures required explorer backend services as a docker compose file, edit that if you want to customize ports, parameters like batches polling interval. It's user responsibility to adjust corresponding JSON app configs if ports are changed in this file.

Why ❔

Currently, running the block-explorer requires users to manually pull the repository, install all dependencies, prepare database, modify configurations, build the project, and then run it. This PR simplifies the process, allowing users to run the explorer effortlessly with a few commands.

Checklist

• PR title corresponds to the body of PR (we generate changelog entries from PRs).
• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• Code has been formatted via zk fmt and zk lint.