fix: use correct encoding for L1 data fee of EIP2718 transactions

[Thegaram]

1. Purpose or design rationale of this PR

EIP2718 defines the byte encoding as Type || Payload, but EncodeRLP returns an actual RLP array, i.e. it prepends the marshaled result with one or more bytes. We should use MarshalBinary instead. Note: The behavior of EncodeRLP and MarshalBinary is identical for legacy transactions, so this is not a breaking change.

This PR also adds an upper bound on L1DataFee to ensure these values don't overflow in the tracing/circuit code. Technically, this is a breaking change, but in practice such high data fee values never occur on Scroll.

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• fix: A bug fix

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes