Increase `MaxFrameLen` and `MaxInputSize` for alt-da

**Is your feature request related to a problem? Please describe.**

When using alt-da, we found that these two parameters were limiting alt-da’s throughput.

- https://github.com/ethereum-optimism/optimism/blob/ddc37daa49558c2fb5c1a92e694eeb7de5942e00/op-batcher/batcher/service.go#L217
- https://github.com/ethereum-optimism/optimism/blob/ddc37daa49558c2fb5c1a92e694eeb7de5942e00/op-node/rollup/derive/frame.go#L14

With max-l1-txbytes set to 130k, we’re only able to achieve around 20 TPS on our testnet. Additionally, if max-l1-bytes exceeds maxFrameLen, the op-node will fail to parse the frame. Therefore, these two parameters need to be adjusted simultaneously.

**Describe the solution you'd like**

We would like to adjust the size of these two parameters or add logic specifically for alt-da, so that when using alt-da, a higher limit can be achieved, allowing for greater throughput.

Specifically, we would like to set both parameter to 4mb for altda.

Start by reading the MaxInputSize setting in op-batcher/batcher/service.go and MaxFrameLen in op-node/rollup/derive/frame.go, then trace how alt-da uses these limits. Confirm how the two values interact when max-l1-bytes exceeds maxFrameLen. Done means alt-da supports the requested higher limit without op-node frame parsing failures.

Written by the indexing model from the issue text.