feat: add hedera docs (#34)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **New Features**
- Updated the testnet name from "Mumbai Testnet" to "Amoy Testnet" in
the Polygon guide.
- Changed references from interacting with Polygon to Arbitrum nodes in
the related guides.
- Updated references from interacting with Polygon to Optimism nodes in
the Optimism guides.
- Added new guides for Hedera network overview, node types, and
connecting to a Hedera node.
- Updated references from Polygon zkEVM to Hedera in smart contracts IDE
documents.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: insider89

docs/blockchain-guides/4_Polygon/1_polygon-the-basics.md

@@ -8,7 +8,7 @@ Polygon has its own cryptocurrency, called MATIC.
 
 ## Mainnet and Testnet
 
-SettleMint supports both the Polygon **Mainnet** and the **Mumbai Testnet**.
+SettleMint supports both the Polygon **Mainnet** and the **Amoy Testnet**.
 
 The Mainnet is the primary public Polygon production blockchain, where actual-value transactions take place. Each transaction requires payment of a transaction fee, payable in the native coin MATIC. The Testnet is an instance of the blockchain to be used for testing and experimentation. There are also coins used in the Testnet but they have no value, so there is no risk of real fund.
 

…ides/8_Arbitrum/1_arbitrum-the-basics.md …ides/7_Arbitrum/1_arbitrum-the-basics.mddocs/blockchain-guides/8_Arbitrum/1_arbitrum-the-basics.md renamed to docs/blockchain-guides/7_Arbitrum/1_arbitrum-the-basics.md docs/blockchain-guides/8_Arbitrum/1_arbitrum-the-basics.md renamed to docs/blockchain-guides/7_Arbitrum/1_arbitrum-the-basics.md

@@ -2,4 +2,4 @@
 
 All nodes running in SettleMint are configured to be **archive nodes**, meaning they all include all previous states of a given blockchain since its origin.
 
-[Learn here how to interact with your Polygon node.](3_arbitrum-connect-to-a-node.md)
+[Learn here how to interact with your Arbitrum node.](3_arbitrum-connect-to-a-node.md)

…ides/8_Arbitrum/2_arbitrum-node-types.md …ides/7_Arbitrum/2_arbitrum-node-types.mddocs/blockchain-guides/8_Arbitrum/2_arbitrum-node-types.md renamed to docs/blockchain-guides/7_Arbitrum/2_arbitrum-node-types.md docs/blockchain-guides/8_Arbitrum/2_arbitrum-node-types.md renamed to docs/blockchain-guides/7_Arbitrum/2_arbitrum-node-types.md

@@ -49,7 +49,7 @@ To be able to deploy your smart contract set on the blockchain you need to have
 
 ## Template library
 
-Every instance of the IDE contains a set of pre-built smart contract templates. These templates are easily customizable to match your specific use case. [Discover the smart contract set templates for Arbitrum.](../8_Arbitrum/Template-library/1_arbitrum-erc-20.md)
+Every instance of the IDE contains a set of pre-built smart contract templates. These templates are easily customizable to match your specific use case. [Discover the smart contract set templates for Arbitrum.](../7_Arbitrum/Template-library/1_arbitrum-erc-20.md)
 
 ## Generative AI plugin
 

…Arbitrum/3_arbitrum-connect-to-a-node.md …Arbitrum/3_arbitrum-connect-to-a-node.mddocs/blockchain-guides/8_Arbitrum/3_arbitrum-connect-to-a-node.md renamed to docs/blockchain-guides/7_Arbitrum/3_arbitrum-connect-to-a-node.md docs/blockchain-guides/8_Arbitrum/3_arbitrum-connect-to-a-node.md renamed to docs/blockchain-guides/7_Arbitrum/3_arbitrum-connect-to-a-node.md

@@ -1,4 +1,4 @@
 {
   "label": "Arbitrum",
-  "position": 8
+  "position": 7
 }