test(datafusion): add Lumina index build procedure

[liujiwen-up]

Purpose

Linked PR: #347

Expose the core Lumina index build capability through DataFusion SQL so users can build a Lumina global vector index with a CALL sys.create_lumina_index(...) statement, then query it through the existing vector_search table function.

Brief change log

• Add CALL sys.create_lumina_index(table => ..., index_column => ...) to DataFusion procedures.
• Wire optional Lumina builder settings through index_type and comma-separated options => 'key=value,...' arguments.
• Add procedure error coverage for missing index_column, invalid index type, and malformed options.
• Add an ignored native Lumina E2E test that writes vector data, builds the Lumina index via SQL, verifies $table_indexes, and runs vector_search.
• Add a CI step to run the native Lumina DataFusion E2E test with the vortex feature after installing the Lumina native library.
• Document the new SQL procedure and options syntax.

Tests

• cargo fmt: passed
• cargo check -p paimon-datafusion: passed
• cargo test -p paimon-datafusion --test procedures create_lumina_index: passed, 3 tests
• cargo test -p paimon-datafusion --features vortex vector_search_tests::test_lumina_build_then_vector_search_query -- --ignored --exact --list: passed, verifies the ignored native E2E test compiles and is discoverable

API and Format

Adds a DataFusion SQL procedure surface for an existing core Lumina index build API. No storage format, manifest format, or public Rust API changes are introduced by this PR.

Documentation

Updated docs/src/sql.md with the create_lumina_index procedure and optional options example.

[QuakeWang]

Please rebase main.

[QuakeWang]

Non-blocking: this wording suggests index_type controls the index identifier written to the manifest. The builder accepts lumina-vector-ann for compatibility, but newly built indexes are canonicalized and stored as lumina. Could we clarify that here to avoid exposing a misleading contract?

[JingsongLi]

+1