[BugFix] Support Fast Schema Evolution v2 for DELETE in shared-data

[banmoy]

Why I'm doing:

DELETE needs to carry the table schema identity so BE can reliably interpret delete predicates under fast schema evolution v2, and update tablet metadata schema during publish when required.

What I'm doing:

• Add schema_key to DeleteDataRequest (proto) to identify the table schema used to generate the delete predicate
• FE: build TableSchemaKeyPB from db/table/base-index schema id in DeleteMgr, plumb it through LakeDeleteJob, and attach it to the delete RPC request
• BE: accept optional schema_key in LakeServiceImpl::delete_data and persist it into the txn log via Tablet::delete_data(...)
• Add backend lake delete gtest coverage for both “without schema key” (backward compatible) and “with schema key” (schema evolution v2)
• Add frontend unit test to verify the delete request contains the expected schema key fields

Fixes #65706

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
  • This pr needs auto generate documentation
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 4.0
  • 3.5
  • 3.4
  • 3.3

---

Note

Enables DELETE to carry the table schema identity for fast schema evolution v2 while remaining backward compatible.

• Proto: add optional schema_key to DeleteDataRequest in lake_service.proto
• FE: build TableSchemaKeyPB in DeleteMgr, plumb through LakeDeleteJob, and set on DELETE RPC
• BE: accept optional schema_key in LakeServiceImpl::delete_data and pass to Tablet::delete_data(...)
• Storage: extend Tablet::delete_data to persist schema_key into op_write txn log
• Tests: add BE lake delete tests (with/without schema_key) and FE unit test verifying request carries expected schema_key

^{Written by Cursor Bugbot for commit 01ac897. This will update automatically on new commits. Configure here.}

[alvin-celerdata]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no bugs!

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 8 / 8 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/lake/delete/LakeDeleteJob.java	3	3	100.00%	[]
🔵	com/starrocks/load/DeleteMgr.java	5	5	100.00%	[]

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 5 / 5 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	be/src/service/service_be/lake_service.cpp	2	2	100.00%	[]
🔵	be/src/storage/lake/tablet.cpp	3	3	100.00%	[]

[alvin-celerdata]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no bugs!

[github-actions]

@Mergifyio backport branch-4.0

[mergify]

backport branch-4.0

✅ Backports have been created

Details

• #67874 [BugFix] Support Fast Schema Evolution v2 for DELETE in shared-data (backport #67456) has been created for branch branch-4.0 but encountered conflicts