regenerate all nitro-client composes with secondary-beacon-url fallback

Adds --parent-chain.blob-client.secondary-beacon-url=${ETHEREUM_<L1>_BEACON_REST_FALLBACK}
to all nitro clients using ethereum L1 (non-arbitrum l1_network_name).
Chains with l1_network_name=arbitrum (apechain, opencampuscodex) remain unchanged
as the flag is inside the non-arbitrum guard.

Generated from templates/clients/nitro.yml + default.env changes in PR #4332.

arb/nitro/real-mainnet-nitro-archive-pebble-hash.yml

@@ -74,6 +74,7 @@ services:
       - --node.sequencer=false
       - --node.staker.enable=false
       - --parent-chain.blob-client.beacon-url=${ETHEREUM_MAINNET_BEACON_REST}
+      - --parent-chain.blob-client.secondary-beacon-url=${ETHEREUM_MAINNET_BEACON_REST_FALLBACK}
       - --parent-chain.connection.url=${ETHEREUM_MAINNET_EXECUTION_RPC}
       - --persistent.chain=/root/.arbitrum/real-mainnet-archive
       - --persistent.db-engine=pebble