Require JDK Vector API at runtime

[pettyjamesm]

Description

Makes the JDK Vector API extensions (JEP 508) required by Trino at runtime.

Before this change, code in the parquet reader would attempt to discover whether the API was enabled via reflection and gracefully fall back to scalar code when not found at runtime. This worked, but required any SIMD implementations to be kept fully isolated such that SIMD related code would only be loaded at runtime by the JVM if enabled which is onerous to maintain as we add more SIMD logic throughout the engine. Requiring this API to be enabled at runtime allows us to write code that need not use reflection tricks and separate classes to detect and isolate SIMD implementations from scalar code.

Additional context and related issues

• Add support for vectorized null suppression for block serde #26919 Adding more Vector API usages for block serialization
• Launcher code already enables the vector API by default

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## General
* Require the JDK Vector API to be enabled at runtime ({issue}`27340`)

[martint]

I don't think this is needed. The launcher enables it automatically, so there's nothing for users to do.

[pettyjamesm]

Shall I rephrase this to make it clear the launcher already sets that flag, or just remove the section altogether? I've rephrased this section to make it more clear that the launcher sets the flag, but am happy to remove it altogether if you'd prefer.

[martint]

I would remove it altogether. It's a detail users shouldn't be concerned with -- we handle everything that's needed under the covers.

[pettyjamesm]

Ok, removed.

[raunaqmorarka]

I think it is good idea to mention it because we should showcase that we're actually using some cool new Java features. Also, developers launch Trino process without going through trino launcher and the information about adding the vector module as a requirement will avoid some confusion.

[pettyjamesm]

Which developer section should I add a mention of this to?

[martint]

Somewhere in here: https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md, which is linked from https://trino.io/docs/current/develop.html

[wendigo]

If launcher is used, vector is linked by default: https://github.com/airlift/launcher/blob/master/src/main/go/args/java_static_config.go#L8

[pettyjamesm]

Will follow up with docs in a subsequent PR. The relevant bits to include in DEVELOPMENT.md might merit some additional discussion that isn't necessary to block this PR on.

[pettyjamesm]

Opened #27342

[findepi]

Before this change, code in the parquet reader would attempt to discover whether the API was enabled via reflection and gracefully fall back to scalar code when not found at runtime.

Do you know why it was done so?

[pettyjamesm]

Do you know why it was done so?

Presumably because we wanted to fallback gracefully when the API was not enabled (it's an incubating API, after all)

[wendigo]

@findepi I think that we assumed at that time, that we don't want to require vector API as we are unsure of its stability. Since then, it proved stable and the only reason this is incubating is its reliance on the Valhalla.

[martint]

It was from the days where we required Java 17 as the minimum version, and before we started tracking the latest JVM version. There was no canonical version to target. So, it was really an optional feature at the time.