IGNITE-13286 Support Java records in binary marshaller

[kush2439p]

SummarynnRoutes Java records through Ignite's optimized Java-serialization path, avoiding Unsafe.objectFieldOffset() on immutable record fields.nn## Root causennHibernate 7 uses a serializable record for QueryResultsCacheImpl.CacheItem. Ignite's reflective binary marshaller attempts to obtain unsafe offsets for record fields, which modern JDKs reject.nn## Changesnn- Detect records without introducing a Java 16 compile-time dependency.n- Use OptimizedMarshaller for records.n- Make the developer warning accurately include records.n- Add a runtime-compiled serializable-record round-trip regression test; it runs on JDK 16+ and skips on older JDKs.nn## Verificationnn- Rebased on current ignite-2.17andgit diff --check passes.n- All 4,531 ignite-core production sources compile successfully on JDK 25.n- Focused test execution is blocked during unrelated full test compilation because JDK 25 removed Thread.suspend()andThread.resume(), which legacy Ignite tests still reference. A supported JDK 17 is not installed locally.n- Existing GitHub check failures are fork checkout-security refusals before code execution, not test failures.nnFixes #13286

[kush2439p]

Fixes the Hibernate 7 query-cache incompatibility caused by Java records.
Hibernate’s QueryResultsCacheImpl.CacheItem is now a record, while Ignite’s reflective binary marshaller calls sun.misc.Unsafe.objectFieldOffset(), which is unsupported for record fields on modern JDKs.
This change detects records without adding a Java 16 compile-time dependency and routes them through Ignite’s optimized Java-serialization path, which supports serializable records.

[kush2439p]

Hi maintainers, following up on this PR since it has been open for several weeks without review. The record-handling fix and regression coverage are ready for review, and I am happy to rebase or revise the approach based on feedback. Thank you.