[FLINK-36350][hotfix] Fix IllegalAccessError in JDK 17 due to kryo InstantiatorStrategy changed

[codenohup]

What is the purpose of the change

Fix IllegalAccessError in JDK 17 due to kryo InstantiatorStrategy changed.
Detail informations see JIRA 36350

Brief change log

• use kryo StdInstantiatorStrategy rather than DefaultInstantiatorStrategy in org.apache.flink.api.java.typeutils.runtime.kryo.KryoSerializer#getKryoInstance

Verifying this change

This change is already covered by existing tests.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: yes
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• 2bd2b8d Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build