feat(jsonrpc): add resource restrict for jsonrpc

[317787106]

What does this PR do?

Adds configurable resource limits to the JSON-RPC endpoint to prevent memory exhaustion and abuse from oversized requests or responses. Closes #6632

Changes:

1. Batch size limit (node.jsonrpc.maxBatchSize, default: 100)

   • Validates the array length of batch JSON-RPC requests before dispatching.
   • Requests exceeding the limit are rejected with error code -32005 (exceed limit).
   • The check is skipped when maxBatchSize ≤ 0 (no limit).

2. Response size limit (node.jsonrpc.maxResponseSize, default: 25 MB)

   • Introduces BufferedResponseWrapper: intercepts getOutputStream() and getWriter() writes into an in-memory buffer. When a write would exceed the configured limit, it sets an overflow flag and resets the buffer instead of continuing to accumulate bytes, bounding worst-case memory usage to at most maxResponseSize.
   • Introduces CachedBodyRequestWrapper: replays the pre-read request body via both getInputStream() and getReader(), so the body can be inspected before being forwarded to JsonRpcServer.
   • After the handler returns, the servlet checks isOverflow() and — if set — discards the partial buffer and returns error code -32003 (response too large).

3. Address list limit (node.jsonrpc.maxAddressSize, default: 1000)

   • In LogFilter, validates the address array length in eth_getLogs / eth_newFilter requests.
   • Requests exceeding the limit are rejected with JsonRpcInvalidParamsException.

4. Structured JSON-RPC error responses

   • writeJsonRpcError uses ObjectMapper to build error responses safely, avoiding JSON injection from error messages.
   • Error codes follow the JSON-RPC 2.0 spec: -32700 parse error, -32005 exceed limit, -32003 response too large.

Why are these changes required?

• Without limits, a client can send an arbitrarily large batch, trigger an expensive query with many addresses, or force the node to serialize a massive response — all of which cause unbounded memory growth.
• The response buffer caps worst-case allocation to maxResponseSize and fails fast rather than buffering the entire response before checking.

Configuration

node {
  jsonrpc {
    # Max JSON-RPC batch array size; 0 = no limit
    maxBatchSize = 100
    # Max response body in bytes (default 25 MB)
    maxResponseSize = 26214400
    # Max address entries in eth_getLogs / eth_newFilter
    maxAddressSize = 1000
  }
}

This PR has been tested by:

• Unit tests (BufferedResponseWrapperTest)
• Manual testing