Update chain ID references from 'elystestnet-1' to 'elysicstestnet-1'… (

#1049)

* Update chain ID references from 'elystestnet-1' to 'elysicstestnet-1' across multiple files

- Changed the chain ID in configuration files, scripts, and documentation to reflect the new test network name.
- Removed the 'network.md' and 'troubleshooting.md' files as they are no longer needed.
- Ensured consistency in CLI command examples by updating the chain ID in various scripts and usage documentation.

This update improves clarity and aligns with the current network naming conventions.

* Refactor CLI commands and documentation for consistency and clarity

- Removed redundant `keyring-backend=test` from multiple CLI commands across various scripts to streamline usage.
- Updated command examples in documentation and scripts to remove unnecessary parameters, enhancing readability and usability.
- Adjusted references to the `elysicstestnet-1` chain ID in scripts and documentation to ensure uniformity.
- Improved the clarity of the `README.md` and other documentation files by refining command examples and descriptions.
- Deleted obsolete files such as `genesis.json`, `config.yml`, and `readme.md` from the `chain` directory to clean up the repository structure.

These changes enhance the user experience by providing clearer instructions and reducing potential confusion in command usage.

* Remove testnet configuration file

- Deleted the `testnet.yml` configuration file, which contained account details, token definitions, and other network parameters.
- This cleanup helps streamline the repository by removing obsolete configurations that are no longer needed.

---------

Co-authored-by: Abhinav Kumar <[email protected]>

architecture.md

@@ -50,21 +50,9 @@ The diagram below illustrates the architecture of Elys Network, outlining its va
 
 The interaction flow between layers is depicted with arrows. Data from the Core Components feeds into the Data Layer. The Liquidity Management layer uses this data to manage liquidity, which is then aggregated in the Pool Aggregation layer. Trading mechanisms utilize the pooled liquidity for various trading activities. The Revenue Model layer ensures economic incentives and sustainability of the system.
 
-## Boilerplate Generation
-
-The boilerplate was generated using `ignite CLI`, which provides a convenient way to generate new chains, modules, messages, and more. The initial modules that are part of the repository include `AssetProfile` and few others, both of which were generated using the `ignite CLI`.
-
-`AssetProfile` requires all changes to go through governance proposals (i.e., adding, updating, or deleting an asset profile entry). Similarly, any modules that expose parameters must require governance proposals to update the module parameters.
-
-## Configuration File
-
-The repository also includes a `config.yml` file, which provides a convenient way to initiate the genesis account, set up a faucet for testnet, define initial validators, and override initial genesis states. Although `ignite` provides the network layer that allows for easy onboarding of new validators to a chain network, the `config.yml` file can be used to specify additional configurations.
-
-In the current `config.yml` file, additional denom metadata has been defined to allow for easy setting of the ELYS amount using any exponent (decimal precision) following the EVMOS good practices. The governance params have also been overridden to reduce the voting period to 20 seconds for local test purposes. Multiple `config.yml` files can be created for each environment (local, testnet, mainnet) with their specific parameters.
-
 ## Denom Units
 
-The `denom_units` property is an array of objects defined in the [config.yml](./config.yml) file, with each object defining a single denomination unit. Each unit object has three properties - `denom`, `exponent`, and `aliases`.
+The `denom_units` property is an array of objects, with each object defining a single denomination unit. Each unit object has three properties - `denom`, `exponent`, and `aliases`.
 
 For the ELYS token, there are three denomination units defined with aliases: