writeReplayMesssage

This would be an L2 action. I think that this should take a transaction hash and a gas limit, we would
1. (optionally) verify that the transaction had a FailedRelayedMessage event emitted
2. fetch the calldata of the transaction
3. call relayMessage on the L2 cross domain messenger with the calldata from the first, (maybe new min gas limit?

See notes on this and gas limit here https://community.optimism.io/docs/protocol/deposit-flow/#replays-in-action

Start by reading the replay notes in the linked Optimism deposit-flow documentation and the existing L2 action patterns in op-viem. Trace how a transaction hash, FailedRelayedMessage, calldata, gas limit, and relayMessage relate before deciding the required behavior. Done means the action has an agreed gas-limit policy and reliably replays the intended message.

Written by the indexing model from the issue text.