Panama implementation of float-byte vector ops

[thecoop]

Followon from #122381, introduce vectorized operations for float-byte comparisons

JMH shows a ~16x speedup:

Benchmark                                  (dims)  (docType)  (function)  (queryType)  (type)  Mode  Cnt    Score   Error  Units
DistanceFunctionBenchmark.benchmark          1024       BYTE         DOT        FLOAT  BINARY  avgt    2  880.346          ns/op
DistanceFunctionBenchmark.vectorBenchmark    1024       BYTE         DOT        FLOAT  BINARY  avgt    2   55.105          ns/op

Unrolling the loop doesn't give any additional performance benefit here, so I've left it as-is (it looks like hotspot may already be unrolling it itself)

[elasticsearchmachine]

Pinging @elastic/es-search-relevance (Team:Search Relevance)

[benwtrent]

Not sure how to test as part of Elasticsearch, as this is new functionality we don't have performance tests for these operations yet...

We should at a minimum add some clauses here: ESVectorUtilTests (missing for some other things I think). This way we capture that we are actually doing the math correct with various random vector sizes.

For performance, we should add a new JMH benchmark if possible for folks to run in the future.

[thecoop]

The JMH tests need some rework to support heterogenous types - let me take a closer look at the infrastructure...

[thecoop]

JMH tests refactored in #124351 ready for this implementation