docs(native): Add runtime metrics documentation

[garimauttam]

Description

Adds comprehensive documentation for presto_cpp.worker_runtime_uptime_secs and all other undocumented runtime metrics.

Related Issue

Resolves #27007

Changes

• Created new presto_cpp/metrics.rst documenting 60+ runtime metrics
• Updated presto-cpp.rst to include metrics in table of contents
• Updated features.rst to reference the comprehensive metrics docs
• Organized metrics into categories (executor, HTTP, task, driver, OS, etc.)

Testing

• Built documentation successfully with ./build
• Verified all cross-references work correctly
• Reviewed generated HTML output

Checklist

• Documentation follows existing format and style
• All metrics from Counters.h are documented
• Follows Conventional Commits format
• References issue fix (docs): Add documentation for runtime metrics #27007

Summary by Sourcery

Document native runtime metrics for Presto C++ and integrate the new metrics reference into the existing documentation structure.

Documentation:

• Add a new presto_cpp/metrics.rst page providing comprehensive documentation for Presto C++ runtime metrics, including uptime and other counters.
• Update presto-cpp.rst to surface the new metrics documentation in the table of contents.
• Update presto_cpp/features.rst to reference the consolidated runtime metrics documentation.

== NO RELEASE NOTE ==

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: garimauttam / name: Garima Uttam (189cb37, 6b76815, 1606534, 838968d, 99fb51a, a43c32a, af496a6, c758c6f, daca6da, e58f434, f1cb7f4)

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[steveburnett]

Thanks for all of this! Just a nit of phrasing.

[garimauttam]

Resolved comment.

[steveburnett]

LGTM! (docs)

Pull updated branch, new local doc build, looks good. Thanks!

[garimauttam]

Thanks for the review!
The maven-checks failure seems unrelated to this change and likely due to recent master updates. I’ll re-run CI and update.

[aditi-pandit]

Thanks @garimauttam for this code.

There are several conflicts between this code and #26875 that was submit recently. Please can you rebase to help us continue the review more effectively.

@agrawalreetika

[garimauttam]

Sure will rebase it.
Thanks

[steveburnett]

Noticed a formatting nit throughout. Please address this when you can.

[steveburnett]

LGTM! (docs)

Pull updated branch, new local doc build, looks good. Thanks for the update!