docs: add test4 config & update testnets section (#2576)

## Description

This PR updates the Network Configuration page for test4, as well as the
testnets page. It also fixes a broken :::warning block.

<details><summary>Contributors' checklist...</summary>

- [x] Added new tests, or not needed, or not feasible
- [x] Provided an example (e.g. screenshot) to aid review or the PR is
self-explanatory
- [x] Updated the official documentation or not needed
- [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message
was included in the description
- [x] Added references to related issues and PRs
- [x] Provided any useful hints for running manual tests
- [x] Added new benchmarks to [generated
graphs](https://gnoland.github.io/benchmarks), if any. More info
[here](https://github.com/gnolang/gno/blob/master/.benchmarks/README.md).
</details>

docs/concepts/namespaces.md

@@ -7,7 +7,7 @@ id: namespaces
 Namespaces provide users with the exclusive capability to publish contracts under their designated namespaces,
 similar to GitHub's user and organization model.
 
-:::warn Not enabled
+:::warning Not enabled
 
 This feature isn't enabled by default on the portal loop chain and is currently available only on test4.gno.land.
 

docs/concepts/testnets.md

@@ -43,6 +43,21 @@ For more information on the Portal Loop, and how it can be best utilized,
 check out the [Portal Loop concept page](./portal-loop.md). Also, you can find
 the Portal Loop faucet on [`gno.land/faucet`](https://gno.land/faucet).
 
+## Test4
+Test4 a permanent multi-node testnet.
+
+- **Persistence of state:**
+  - State is fully persisted unless there are breaking changes in a new release,
+    where persistence partly depends on implementing a migration strategy
+- **Timeliness of code:**
+  - Versioning mechanisms for packages & realms will be implemented for test4
+- **Intended purpose**
+  - Running a full node, testing validator coordination, deploying stable Gno
+    dApps, creating tools that require persisted state & transaction history
+- **Versioning strategy**:
+  - Test4 is the first gno.land testnet to be release-based, following releases
+of the Gno tech stack.
+
 ## Staging
 Staging is a testnet that is reset once every 60 minutes.
 
@@ -57,24 +72,6 @@ Staging is a testnet that is reset once every 60 minutes.
 - **Versioning strategy**:
   - Staging is reset every 60 minutes to match the latest monorepo commit
 
-## Test4 (upcoming)
-Test4 (name subject to change) is an upcoming, permanent, multi-node testnet. 
-To follow test4 progress, view the test4 milestone
-[here](https://github.com/gnolang/gno/milestone/4).
-Once it is complete, it will have the following properties:
-
-- **Persistence of state:**
-  - State is fully persisted unless there are breaking changes in a new release,
-where persistence partly depends on implementing a migration strategy
-- **Timeliness of code:**
-  - Versioning mechanisms for packages & realms will be implemented for test4
-- **Intended purpose**
-  - Running a full node, testing validator coordination, deploying stable Gno 
-dApps, creating tools that require persisted state & transaction history
-- **Versioning strategy**:
-  - Test4 will be the first testnet to be release-based, following releases of
-the Gno tech stack.
-
 ## TestX
 These testnets are deprecated and currently serve as archives of previous progress.
 

docs/reference/network-config.md

@@ -7,8 +7,8 @@ id: network-config
 | Network     | RPC Endpoint                      | Chain ID      | 
 |-------------|-----------------------------------|---------------|
 | Portal Loop | https://rpc.gno.land:443          | `portal-loop` |
-| Testnet 4   | upcoming                          | upcoming      |
-| Testnet 3   | https://rpc.test3.gno.land:443    | `test3`       |
+| Test4       | https://rpc.test4.gno.land:443/   | `test4`       |
+| Test3       | https://rpc.test3.gno.land:443    | `test3`       |
 | Staging     | http://rpc.staging.gno.land:36657 | `staging`     |
 
 ### WebSocket endpoints