Bump hazelcast from 3.11 to 5.3.0 in /payara-micro/payara-micro-examples

[dependabot[bot]]

Bumps hazelcast from 3.11 to 5.3.0.

Release notes

Sourced from hazelcast's releases.

v5.3.0

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform 5.3.0 release. The numbers in the square brackets refer to the issues and pull requests in Hazelcast's GitHub repository.

New Features

• Connector for Kafka Connect source (BETA): Import data from an external system directly into a Hazelcast data pipeline without the need of a Kafka cluster.
• Connector for MongoDB (BETA): Read and write from/to MongoDB via this connector and execute SQL queries on Mongo collections directly from Hazelcast.
• Partition-Aware SQL Client: Send the SQL commands only to the members having the relevant data, which reduces the network hops and improves the query performances.
• Data connection support in SQL: data connections and mappings using them can be managed using SQL commands.

Breaking Changes

• Renamed the DataLinkFactory interface as DataConnection. #24224
• Removed the TO_ROW function as it is obsolete, you can use CAST (udtObj AS JSON) instead. #23808
• SQL mappings for internal maps (__sql.catalog and __jet.*) cannot be created anymore. #24282
• Changed the default cloud coordinator URL from coordinator.hazelcast.cloud to api.viridian.hazelcast.com. The default configuration now connects to https://viridian.hazelcast.com/sign-in?next=/ instead of Hazelcast Cloud. If you want to continue accessing your Hazelcast Cloud clusters, you need to set the hazelcast.client.cloud.url property to https://coordinator.hazelcast.cloud in your configuration. #23290

Enhancements

Cloud

• Hazelcast was sending requests to Kubernetes API when deploying an application with embedded Hazelcast and service-dns (DNS lookup mode) specified to a Kubernetes cluster. This was causing the requests to be unsuccessful and the application not to start. This mechanism has been improved by creating Kubernetes client only for the DNS lookup mode. #23883
• When advanced networking is enabled, the Kubernetes discovery plugin might have been discovering several endpoints (per each port) for each member's pod. The discovery plugin now matches only the private IP per endpoint, ignoring the port values. #23766
• Added support of link:https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/#:~:text=Posted%20On%3A%20Oct%203%2C%202022,depth%20against%20unauthorized%20metadata%20access.[IMDSv2^] for Hazelcast's AWS Discovery plugin. #23545
• Added the support of discovering ECS and EC2 members on AWS. See xref:deploy:deploying-on-aws.adoc[Deploying a Cluster on Amazon AWS]. #22411

Storage

• Added support of generating suggested Data Definition Language (DDL) for a map with High-Density Memory Store and having no indexes. #24054
• Disk tier option of Tiered Storage is now disabled by default. #23747

NOTE: Tiered Storage feature is still in BETA stage.

Distribution

• Hazelcast no longer depends on JRuby; the JRuby ScriptFactory dependency must be explicitly added to the application. #23355
• Added the Kafka Connect extension to the distribution. #23312
• Shaded dependencies for Hazelcast Platform have been combined in a dedicated package (com.hazelcast.shaded). #23124

Networking

• Added socket options for per-socket keep-alive configuration: keep-count, keep-idle-seconds, and keep-interval-seconds. You can set these options using either the advanced network configurations or Hazelcast system properties. See Configuring TCP Keep-Alive. #24050

SQL Engine

... (truncated)

Commits

• a3ae01d Upgrade version to 5.3.0
• dc39625 5.3.0 release notes fix (#24591)
• c20c94b Update release_notes.txt
• 465d6b2 Update release_notes.txt
• ac5e0e3 Prepare release 5.3.0
• 9d9d7aa Disallow adding listener to completed jobs [HZ-2254] (#24197)
• 4a03057 Fix nightly MySql data connection test (#24556)
• 77461f6 Increase timeout in GenericMapStoreIntegrationTest#testClear [HZ-2430] (#24551)
• e1727aa Tweak stream-to-stream fault tolerance stress test timeout and events count (...
• f1f6e5e Prevent data connection creation with a wrong type (#24500)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/payara/Payara-Examples/network/alerts).