[core][flink] Publish primary-key vector indexes on write

[JingsongLi]

Summary

Activates primary-key vector index maintenance in the write path on top of #8549 and #8562. Complete Level 1 compact files become ANN sources, and bucket-local ANN additions and removals are published with the same compact increment as their source data transition.

Changes

• Force lookup compaction to rewrite Level 0 files for both deduplicate and partial-update tables, ensuring vector indexes are built only from complete Level 1 rows.
• Create and restore a bucket-local vector index maintainer for primary-key table writers using the configured vector field, metric, algorithm, and field-scoped index options.
• Publish ANN additions and removals through the matching compact increment and retain maintainer state across writer checkpoints.
• Restore active source-backed ANN metadata from filesystem manifests without requiring an auxiliary directory index.
• Extend the existing write-restore and Flink coordination signatures directly to round-trip active vector index payloads, adapting all callers without compatibility overloads.

Testing

• Verify deduplicate and partial-update lookup compaction both rewrite Level 0 files.
• Verify vector index additions and removals are attached to the same compact data transition.
• Verify filesystem writer restore returns active source-backed ANN metadata.
• Verify Flink coordinator restore round-trips ANN metadata with inclusive ordinal ranges.
• Run the related Core suite: 19 tests passed.
• Run the focused Flink coordinator test: 1 test passed.
• Run non-fast Core/Flink compilation with Checkstyle, Spotless, and Maven enforcers.

Notes

• Follows [core] Add bucket-level primary-key vector index maintenance #8562, which introduced bucket-level primary-key vector index maintenance.
• This PR intentionally covers only write publication and restore. Primary-key vector query routing remains a follow-up.

[leaves12138]

Reviewed the latest head. The Level-0 rewrite is correctly scoped to the reachable deletion-vector lookup path, vector payload additions/removals are published with the matching compact increment, and filesystem/Flink restore round-trips the active source-backed payloads consistently. The focused Core tests and the new Flink coordinator test pass locally. LGTM.