feat(query): support experimental table branch

[zhyass]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

This PR brings the previously reviewed and merged table-branch implementation from #19551 to main.

• Original PR: feat(query): support experimental table branch #19551
• feat(query): support experimental table branch #19551 was reviewed and merged into feat_branch; this PR rebases/adapts that implementation onto the current main branch.
• The original review history and discussions remain available on feat(query): support experimental table branch #19551. This PR is intended to land the same feature on main, with compatibility updates required by changes that landed since the original review.

The feature adds experimental table branches for FUSE tables: lightweight writable forks with independent snapshot histories and copy-on-write sharing of existing segments and blocks. It includes branch metadata and lifecycle APIs, branch-qualified table resolution, branch-safe vacuum/GC behavior, and protection for files still referenced by active branches or tags.

Implementation notes

• Add branch metadata keys, protobuf conversion, lifecycle APIs, and GC/undrop retention handling.
• Resolve branch-qualified FUSE tables through catalog and query context APIs.
• Preserve branch and tag history during vacuum2, dropped-table vacuum, and virtual-column vacuum.
• Adapt the original feat(query): support experimental table branch #19551 implementation to current main APIs, including metadata table registration, table-cache eviction, materialized-view integration, and current meta transaction helpers.
• Keep feat: stmt support branch #19774 changes out of this submission; this PR carries feat(query): support experimental table branch #19551 onto main independently.

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Validation performed:

• make lint
• Targeted cargo check for meta app/API/proto conversion/schema test suite, SQL, Fuse storage, and enterprise query crates
• Meta branch key tests: 5 passed
• Ref API tests: 14 passed
• Proto conversion tests passed
• Schema API single-node integration test passed, including branch GC and undrop retention coverage

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

Review context

The feature implementation was already reviewed in #19551 before being merged into feat_branch. Reviewers can focus this round on the adaptation to current main and any integration changes since that review.

AI assistance

• AI usage: An AI coding agent assisted with merging current main, resolving API compatibility issues, running validation, and drafting this PR summary. The responsible human reviewed the feature previously through feat(query): support experimental table branch #19551 and owns this submission.
• Responsible human: @zhyass
• The responsible human has read every line of this diff and can explain each change

---

This change is 

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 70a7f8f7b2

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[zhyass]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eee055f662

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".