Add --l2-gas-limit deployer flag to vanilla and validium deployment docs

and fix stale maintain_sequencer.md links to point to upgrades.md

Author: avilagaston9

docs/l2/deployment/validium.md

@@ -21,6 +21,7 @@ ethrex l2 deploy \
   --committer.l1-address <L1_COMMITTER_ADDRESS> \
   --proof-sender.l1-address <L1_PROOF_SENDER_ADDRESS> \
   --env-file-path <PATH_TO_ENV_FILE> \
+  --l2-gas-limit <L2_GAS_LIMIT> \
   --randomize-contract-deployment
 ```
 
@@ -57,6 +58,7 @@ ethrex l2 deploy \
 > - The `CommonBridge` and `OnChainProposer` contracts are upgradeable and ownable, with implementations behind proxies initialized during deployment. Replace `COMMON_BRIDGE_OWNER_ADDRESS` and `ON_CHAIN_PROPOSER_OWNER_ADDRESS` with the address of the account you want as the owner. The owner can upgrade implementations or perform administrative actions; for more details, see the Architecture section.
 > - The sequencer components (`L1Committer` and `L1ProofSender`) require funded accounts on the target L1 to advance the network. Replace `L1_COMMITTER_ADDRESS` and `L1_PROOF_SENDER_ADDRESS` with the addresses of those accounts.
 > - Replace `PATH_TO_ENV_FILE` with the path where you want to save the generated environment file. This file contains the deployed contract addresses and other configuration details needed to run the L2 node.
+> - Replace `L2_GAS_LIMIT` with the desired L2 block gas limit (defaults to `30000000`). This value is stored in the `CommonBridge` contract and can be updated later by the bridge owner.
 > - L1 contract deployment uses the `CREATE2` opcode for deterministic addresses. To deploy non-deterministically, include the `--randomize-contract-deployment` flag.
 
 ## 2. Start the L2 node
@@ -90,7 +92,7 @@ ethrex l2 \
 > - Replace `L1_PROOF_SENDER_PRIVATE_KEY` and `L1_COMMITTER_PRIVATE_KEY` with the private keys for the `L1_PROOF_SENDER_ADDRESS` and `L1_COMMITTER_ADDRESS` from the deployment step.
 > - Replace `L1_RPC_URL` and `PATH_TO_L2_GENESIS_FILE` with the same values used in the deployment step.
 > - Tune throughput with the gas caps:
->   - The L2 block gas limit is stored on-chain in the `CommonBridge` contract. The sequencer fetches this value on startup. See [Maintain Sequencer](../interacting/maintain_sequencer.md) for how to view and update it.
+>   - The L2 block gas limit is stored on-chain in the `CommonBridge` contract (set during deployment via `--l2-gas-limit`, defaults to 30000000). The sequencer fetches this value on startup. See [Upgrades](./upgrades.md#from-v10-to-v11) for how to view and update it.
 >   - `--committer.batch-gas-limit` (env: `ETHREX_COMMITTER_BATCH_GAS_LIMIT`): Sets the gas limit per batch sent to L1—should be at or above the block gas limit.
 >
 >   You can use either the environment variables or the flags to configure these values.

docs/l2/deployment/vanilla.md

@@ -20,6 +20,7 @@ ethrex l2 deploy \
   --committer.l1-address <L1_COMMITTER_ADDRESS> \
   --proof-sender.l1-address <L1_PROOF_SENDER_ADDRESS> \
   --env-file-path <PATH_TO_ENV_FILE> \
+  --l2-gas-limit <L2_GAS_LIMIT> \
   --randomize-contract-deployment
 ```
 
@@ -56,6 +57,7 @@ ethrex l2 deploy \
 > - The `CommonBridge` and `OnChainProposer` contracts are upgradeable and ownable, with implementations behind proxies initialized during deployment. Replace `COMMON_BRIDGE_OWNER_ADDRESS` and `ON_CHAIN_PROPOSER_OWNER_ADDRESS` with the address of the account you want as the owner. The owner can upgrade implementations or perform administrative actions; for more details, see the Architecture section.
 > - The sequencer components (`L1Committer` and `L1ProofSender`) require funded accounts on the target L1 to advance the network. Replace `L1_COMMITTER_ADDRESS` and `L1_PROOF_SENDER_ADDRESS` with the addresses of those accounts.
 > - Replace `PATH_TO_ENV_FILE` with the path where you want to save the generated environment file. This file contains the deployed contract addresses and other configuration details needed to run the L2 node.
+> - Replace `L2_GAS_LIMIT` with the desired L2 block gas limit (defaults to `30000000`). This value is stored in the `CommonBridge` contract and can be updated later by the bridge owner.
 > - L1 contract deployment uses the `CREATE2` opcode for deterministic addresses. To deploy non-deterministically, include the `--randomize-contract-deployment` flag.
 
 ## 2. Start the L2 node
@@ -88,7 +90,7 @@ ethrex l2 \
 > - Replace `L1_PROOF_SENDER_PRIVATE_KEY` and `L1_COMMITTER_PRIVATE_KEY` with the private keys for the `L1_PROOF_SENDER_ADDRESS` and `L1_COMMITTER_ADDRESS` from the deployment step.
 > - Replace `L1_RPC_URL` and `PATH_TO_L2_GENESIS_FILE` with the same values used in the deployment step.
 > - Tune throughput with the gas caps:
->   - The L2 block gas limit is stored on-chain in the `CommonBridge` contract. The sequencer fetches this value on startup. See [Maintain Sequencer](../interacting/maintain_sequencer.md) for how to view and update it.
+>   - The L2 block gas limit is stored on-chain in the `CommonBridge` contract (set during deployment via `--l2-gas-limit`, defaults to 30000000). The sequencer fetches this value on startup. See [Upgrades](./upgrades.md#from-v10-to-v11) for how to view and update it.
 >   - `--committer.batch-gas-limit` (env: `ETHREX_COMMITTER_BATCH_GAS_LIMIT`): Sets the gas limit per batch sent to L1—should be at or above the block gas limit.
 >
 >   You can use either the environment variables or the flags to configure these values.