docs: Update Analyse.rst with support for Iceberg connector

[Ishaan-2312]

Description

docs: clarify ANALYZE connector support

This change updates documentation to reflect that the ANALYZE statement
is supported by both Hive and Iceberg connectors.

Motivation and Context

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• If adding new dependencies, verified they have an OpenSSF Scorecard score of 5.0 or higher (or obtained explicit TSC approval for lower scores).

Release Notes

== NO RELEASE NOTE ==

Summary by Sourcery

Documentation:

• Clarify and expand ANALYZE command documentation to include Iceberg connector support.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Ishaan-2312 / name: Ishaan Bansal (df1015b)

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the SQL ANALYZE command documentation to describe support and behavior for the Iceberg connector in analyze.rst.

File-Level Changes

Change	Details	Files
Extend ANALYZE documentation to cover Iceberg connector support and behavior.	Add Iceberg connector to the list of connectors supporting ANALYZE, including any prerequisites or limitations. Describe how ANALYZE works for Iceberg tables, including statistics collection semantics and scope. Clarify or align wording so Iceberg behavior is consistent with existing connector docs (e.g., Hive) where applicable.	presto-docs/src/main/sphinx/sql/analyze.rst

---

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.

[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]

Take a look at the comments and let me know if you have questions.

[steveburnett]

Suggested change

	:ref:`Hive connector <hive_analyze>`.
	:ref:`Hive connector <hive_analyze>` and the :ref:`Iceberg connector <iceberg_analyze>`.

Syntax of the Iceberg link fixed - you had added a space after the ref: in the Iceberg link so the current file looked like this in a local doc build.

Local doc builds are helpful to find formatting mistakes. For more information on running local doc builds, see Building the Documentation in the Presto docs README.

[steveburnett]

After fixing the link as mentioned in the other comment, the link does not appear to have a valid destination.

Please edit the link so that it links to a destination.

[steveburnett]

1. Please add

== NO RELEASE NOTE ==

in the PR description to pass the failing but not required for merge test.

2. Please edit the title of the PR to pass the failing and required test.

Maybe something like docs: Update Analyse.rst with support for Iceberg connector.

3. Please resolve the file conflict that is blocking this PR from merge.

[steveburnett]

There are no changes to any files in this PR now so there is nothing to review. A valid link to the Iceberg connector was added to the ANALYZE doc in #27041, which has been merged and is already in the master branch, so a local doc build of this PR is identical to a local doc build of the master branch.

Suggest closing this PR as superseded by #27041.

When you have time, please open a new docs PR to add an example to the Iceberg doc as mentioned in this comment on 27041. I opened issue #27065 which the new docs PR would fix.