ESQL: Add memory accountancy and circuit breaking

[ChrisHegarty]

Currently the ESQL runtime does not use circuit breakers, so is susceptible to OutOfMemoryErrors when working with large amounts of data or performing memory intensive operations . Similar to other parts of Elasticsearch, ESQL should circuit break its allocations and track overall memory usage.

The ESQL runtime on data nodes has a bounded queue in their exchange sink. This queue adds a natural bound to the amount of outstanding pages (and transitively bocks and vectors) that are in use at any one time, but is not sufficient when dealing with data with large numbers of columns or bytes refs that are enormous in size. Additionally, the coordinator may need to hold a lot of data in memory when processing output from the data nodes and/or computing the overall result.

ESQL driver pipelines are executed in a single threaded manner. The general idea is have a circuit breaker per driver, whereby this breaker would "checkout" chunks of memory from it's parent breaker. These chunks would be allotted to the code executing in the driver - a thread local allocation if you will. The driver breaker subsequently request more memory from its parent when this TLA is exhausted. The ESQL runtime will have an overall breaker for all of its allocations on any one particular node, which includes the tasks that it performs as both a data node as well as a coordinator.

A non-exhaustive list of specific tasks:

• Add memory accountancy for blocks and vectors
• Create overall ESQL breaker
• Driver specific breaker (Introduce local block factory #102901)
• Block and Vector creation can start to use a block factory that performs circuit breaking #99826
• Move block and vector creation to a factory instance, allowing to circuit break on creation
• Releasable blocks/vectors - allowing to adjust the circuit breaker
• ESQL: Tracker for tests impacted by the circuit breaker #100147

[elasticsearchmachine]

Pinging @elastic/es-ql (Team:QL)

[elasticsearchmachine]

Pinging @elastic/elasticsearch-esql (:Query Languages/ES|QL)

[elasticsearchmachine]

Pinging @elastic/es-analytics-geo (Team:Analytics)

[ChrisHegarty]

We're in a very good state with regard to memory tracking. And all the substantial subtasks in this meta issue are complete. Closing