align API docs with java-tron v4.8.2

[abn2357]

Summary

Align the HTTP and JSON-RPC API docs with java-tron v4.8.2 behavior (Chinese translation).

• Replace node.maxMessageSize error rows with node.http.maxMessageSize and HTTP 413 SizeLimitHandler behavior
• Add oversized-body HTTP 413 rows to endpoints that lacked them
• Document int64_as_string=true GET flag on applicable endpoints
• Add blockTimestamp to JSON-RPC log outputs
• Document maxLogFilterNum, maxAddressSize, maxResponseSize, maxBatchSize, and data/input alias handling for eth_call, eth_estimateGas, and buildTransaction
• Align documented JSON parse errors with org.tron.json.JSONException after fastjson removal
• Expand smart-contract trigger/constant/estimate error response rows with concrete CONTRACT_VALIDATE_ERROR messages
• Document JSON-RPC safe block tag handling and eth_newFilter pending/safe errors
• Correct JSON-RPC servlet-level error codes for parse errors, invalid requests, oversized responses, batch limits, and internal errors
• Update demo JSONObject import to org.tron.json.JSONObject
• Unify terminology: 区块号 -> 区块高度, 无效果 -> 无影响, abi.encode -> ABI 编码

Test plan

• Verified changed config keys, error messages, and JSON values against java-tron v4.8.2
• Cross-checked against the English docs for parity

[vivian1912]

The API docs were updated for java-tron v4.8.2 behavior, but the machine-readable OpenAPI/OpenRPC definitions were not updated in the same PR.

This creates a contract mismatch for SDK generators, tool integrations, and AI agents. For example, the human docs now describe int64_as_string, CallArguments.input / BuildArguments.input, and blockTimestamp, but docs/api/openapi.yaml, docs/api/openrpc.json, and the per-endpoint files under docs/api/specs/ still omit those fields or response variants.

[abn2357]

The API docs were updated for java-tron v4.8.2 behavior, but the machine-readable OpenAPI/OpenRPC definitions were not updated in the same PR.

This creates a contract mismatch for SDK generators, tool integrations, and AI agents. For example, the human docs now describe int64_as_string, CallArguments.input / BuildArguments.input, and blockTimestamp, but docs/api/openapi.yaml, docs/api/openrpc.json, and the per-endpoint files under docs/api/specs/ still omit those fields or response variants.

Thanks. They are separated for now, and the spec will be updated later. To keep consistency, the maintainer of this repo can merge them together afterwards.
Your suggestion is great, I will consider combining them for future updates.