schemadiff: RangeRotationDistinctStatements partitioning hint

[shlomi-noach]

Description

Follow up to #10234. We change behavior as follows:

• The flag RangeRotationStatements is renamed to RangeRotationDistinctStatements to better describe what it does (as of this PR)
• When two tables are diffed, and partition rotation hint is RangeRotationDistinctStatements, and there are indeed partition rotation changes, then the result is a sequence of diffs (one diff with linked subsequent diffs). If the table definition it self was also diffed (e.g. a modified column), that is allowed, and that will always be the primary diff, to which the partition diffs are appended. If the table is otherwise unmodified, then the primary diff is the first in partition changes.
• As reminder, when RangeRotationStrategy is RangeRotationFullSpec, the above is irrelevant, and the diff results with a single ALTER TABLE, that may include a full partitioning spec.

Related Issue(s)

• schemadiff: analyze and apply ADD PARTITION and DROP PARTITION statements #10234
• schemadiff: tracking issue #10203

Checklist

• "Backport me!" label has been added if this change should be backported
• Tests were added or are not required
• Documentation was added or is not required

Deployment Notes

[github-actions]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
• If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• vtctl command output order should be stable and awk-able.

[dbussink]

I like how allowing this functionality is mostly removing code 😄.