feat: track query memory pool

[fengjiachun]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

When the aggregation operator exceeds memory limits, it may display an error message in this format:

{name}#{id}(can spill: {can_spill}) consumed {size}, peak {peak}

Example:

Resources exhausted: Additional allocation failed for {operator} with top memory consumers (across reservations) as:
  GroupByHashExec#123(can spill: true) consumed 1.2 GB, peak 1.5 GB,
  HashJoinExec#456(can spill: true) consumed 800.0 MB, peak 950.0 MB,
  SortExec#789(can spill: true) consumed 500.0 MB, peak 600.0 MB,
  FilterExec#234(can spill: false) consumed 10.0 MB, peak 15.0 MB,
  ProjectionExec#567(can spill: false) consumed 5.0 MB, peak 8.0 MB.
Error: Failed to allocate additional...

The error message above details memory usage for the top 5 operators consuming the most memory, which helps with troubleshooting. Currently, the top 5 is fixed and does not allow for custom configuration.

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.
• API changes are backward compatible.
• Schema or data changes are backward compatible.