Enable decoding for large RPC requests

[siladu]

This is to support large payloads (in engine_newPayload) at least up to 200MGas block sizes (and a bit more). Limit may need revisiting at larger block sizes.

Max out StreamReadConstraints.maxStringLength for jackson decoding of request and parameters

Create Engine API specific EngineJsonRpcParserHandler and EngineJsonRpcParameter containing modified ObjectMapper.

Go back to globally configured but using a 128MB equivalent limit instead of MAX_VALUE. This aligns with the bodyLimit we were already setting.

A version of this was tested on performance branch via #8791 and #8796
but this PR restricts the changes to Engine API so shouldn't open up external DOS vectors since Engine API is assumed to be restricted to internal networks.

Why the large limit?

Using the large transaction full of zeros test cases from https://github.com/NethermindEth/gas-benchmarks/blob/main/tests-vm/TxDataZero30M_30M.txt :

30M:   ~15M chars = ~15MB
60M:   ~30M chars = ~30MB
200M: ~100M chars = ~100MB
# prediction:
300M: ~150M chars = ~150MB

128MB was already used as the engine API HTTP body limit, so lowering this is a potential breaking change.
128MB is roughly equivalent to 128M chars with UTF-8 encoding.
128MB will support 200Mgas transactions which are used in the performance benchmarking suite.
We should maybe increase this limit even higher if we want to support a 300Mgas full of zeros.

Testing

No visible impact on mainnet sync or operations

This PR is able to parse this large newPayload: https://github.com/NethermindEth/gas-benchmarks/blob/main/tests-vm/TxDataZero200M_200M.txt

Also wrote a custom test to cache this large payload and retrieve with getPayload.

Tested with ethereum/go-ethereum@master/cmd/workload and behaves the same as control.

[ahamlat]

When testing on mainnet, I go this error

{"@timestamp":"2025-06-30T09:23:24,844","level":"ERROR","thread":"vert.x-worker-thread-
1","class":"JsonRpcExecutorHandler","message":"engine_forkchoiceUpdatedV3 - Error streaming JSON-RPC 
response","throwable":" java.io.IOException: io.vertx.core.http.HttpClosedException: Connection was closed\n\tat 
org.hyperledger.besu.ethereum.api.jsonrpc.JsonResponseStreamer.stopOnFailureOrClosed(JsonResponseStreamer.java:85)
\n\tat org.hyperledger.besu.ethereum.api.jsonrpc.JsonResponseStreamer.write(JsonResponseStreamer.java:57)\n\tat 
com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2241)\n\tat 
com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1232)\n\tat 
com.fasterxml.jackson.databind.ObjectWriter._writeValueAndClose(ObjectWriter.java:1290)\n\tat 
com.fasterxml.jackson.databind.ObjectWriter.writeValue(ObjectWriter.java:1098)\n\tat org.hyperledger.besu.ethereum.api.handlers.JsonRpcObjectExecutor.handleJsonObjectResponse(JsonRpcObjectExecutor.ja
va:80)\n\tat 
org.hyperledger.besu.ethereum.api.handlers.JsonRpcObjectExecutor.execute(JsonRpcObjectExecutor.java:58)\n\tat 
org.hyperledger.besu.ethereum.api.handlers.JsonRpcExecutorHandler.lambda$handler$1(JsonRpcExecutorHandler.java:61)\
n\tat java.base/java.util.Optional.ifPresentOrElse(Optional.java:196)\n\tat 
org.hyperledger.besu.ethereum.api.handlers.JsonRpcExecutorHandler.lambda$handler$3(JsonRpcExecutorHandler.java:58)
\n\tat io.vertx.ext.web.impl.BlockingHandlerDecorator.lambda$handle$0(BlockingHandlerDecorator.java:48)\n\tat 
io.vertx.core.impl.ContextImpl.lambda$executeBlocking$5(ContextImpl.java:205)\n\tat 
io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:270)\n\tat 
io.vertx.core.impl.ContextImpl$1.execute(ContextImpl.java:221)\n\tat 
io.vertx.core.impl.WorkerTask.run(WorkerTask.java:56)\n\tat 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)\n\tat 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)\n\tat 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat 
java.base/java.lang.Thread.run(Thread.java:1583)\nCaused by: io.vertx.core.http.HttpClosedException: Connection was 
closed\n"}

[ahamlat]

This PR needs at least the same level of testing as #8847 as it is changing how newPayload requests are deserialized

[ahamlat]

Do we need two constants with the same name and same value in two different files ? Why not keep only one of these ?

[siladu]

Ideally, we should have one set of this config, but these duplicates are an existing issue, not to sort out for this PR IMO

[ahamlat]

LGTM