docs: document gRPC result-bounding server settings (#4823)

[robfrank]

Summary

Documents the three SERVER-scoped gRPC DoS-protection settings introduced in ArcadeData/arcadedb#4823 (bound gRPC result materialization and worker busy-wait).

Added to the SERVER table in src/main/asciidoc/reference/settings.adoc:

Setting	Type	Default	Purpose
server.grpcQueryMaxResultRows	Integer	100000	Hard ceiling on rows the unary ExecuteQuery materializes; exceeding fails with RESOURCE_EXHAUSTED
server.grpcStreamMaxMaterializedRows	Integer	1000000	Max rows StreamQuery MATERIALIZE_ALL buffers before emitting; exceeding fails with RESOURCE_EXHAUSTED
server.grpcStreamWriteTimeoutMs	Long	60000	Max time a StreamQuery worker waits for transport readiness before aborting

These are registered GlobalConfiguration SERVER settings (server.grpc*), distinct from the plugin-level grpc.* keys, so they belong in the SERVER settings table rather than the gRPC plugin section.

Also:

• Added a cross-reference from the gRPC plugin settings section pointing to these bounding knobs.
• Added the missing [[setting-server]] anchor the cross-reference targets.

All marked _(Available since v26.7.1)_ (current dev version is 26.7.1-SNAPSHOT).

Validation

python3 docs-validator.py passes — filenames, anchors, and cross-references all valid.

🤖 Generated with Claude Code

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[gemini-code-assist]

Code Review

This pull request updates the documentation in settings.adoc to introduce three new server settings: server.grpcQueryMaxResultRows, server.grpcStreamMaxMaterializedRows, and server.grpcStreamWriteTimeoutMs. These settings are designed to bound result materialization and protect against limitless or slow clients pinning worker threads and exhausting heap. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.