feat(index): add JVector index support and related builder class

[robfrank]

This pull request introduces comprehensive support for the JVector vector index within ArcadeDB, including dependency management, SQL parser enhancements, and a full end-to-end test suite. The changes enable users to create and manage JVector indexes via SQL, configure vector index parameters, and validate vector data workflows through automated tests.

JVector Index Support and Configuration:

• Added jvector dependency (jvector.version and Maven dependency) to engine/pom.xml to enable vector indexing capabilities. [1] [2]
• Enhanced CreateIndexStatement.java to recognize and validate the JVECTOR index type in SQL statements, including configuration options for dimensions, similarity function, max connections, and beam width. [1] [2]
• Implemented logic in CreateIndexStatement.java to build JVector indexes using user-provided or default configuration, and added callback for indexing progress reporting. [1] [2]

End-to-End Testing:

• Added a new comprehensive E2E test class JVectorSqlE2ETest.java covering schema creation, vector data insertion, retrieval, update, deletion, batch operations, and index management for JVector indexes.

Codebase Maintenance:

• Updated imports in CreateIndexStatement.java to support JVector integration and improve code clarity.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ -0.23%	✅ 41.11%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (25e480f)	73027	46288	63.38%
Head commit (58fa112)	73845 (+818)	46637 (+349)	63.16% (-0.23%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#2530)	1951	802	41.11%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[gramian]

What is the plan for the different distance functions? Will there be a replacement?

[robfrank]

What is the plan for the different distance functions? Will there be a replacement?

I will reimport/rewrite, I've just removed them to have less code around to manage.

Next step, with @lvca is to take some decisions about persistence on disk.