Bump hazelcast from 5.1 to 5.2.1

[dependabot[bot]]

Bumps hazelcast from 5.1 to 5.2.1.

Release notes

Sourced from hazelcast's releases.

v5.2.1

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

==== Hazelcast Platform 5.2.1 ====

Enhancements

• Added the support of discovering ECS and EC2 members on AWS. See Deploying a Cluster on Amazon AWS. #22590

Fixes

• Fixed a memory leak due to incomplete clean-up of backup replica sync operations. #22756
• Fixed an issue where a map was loading old values with map.set() when map store offloading is enabled. #22603
• Fixed an issue where the map entries recovered from persistence were not expiring after their time-to-live durations. #22557
• Fixed an issue where external data store configurations could not be added dynamically. #22464

==== Hazelcast Platform 5.2.0 ====

New Features

• SQL stream-to-stream joins: You can now correlate multiple streams of data with each other using the relational join operation.
• Generic MapStore (BETA): You no longer need to write Java code to get data from an external data store, such as a relational database, into Hazelcast by implementing the MapStore or MapLoader interfaces.
• JDBC connector (BETA): You can now use SQL to connect to and query any database that supports the JDBC interface.
• CP Subsystem Leadership Priority: To ensure the availability of the CP subsystem, you can now transfer CP member leadership to another member: There are cases when some CP members should not act as a leader. For example, a member with high load would not be a good leader, or, in a WAN deployment, members in a primary datacenter may be preferred in order to minimize the latency between the clients and leader. You can transfer the leadership using the cp-member-priority configuration element. See Configuring Leadership Priority.
• User Defined Types (Experimental): You can now query nested objects within Java, compact, and portable mappings using the User Defined Types (UDTs).

Breaking Changes

• Introduced a check to control the versions of Hazelcast Platform members and Hazelcast CLI are matched. Previously, it was possible to submit a job using a different version of CLI from the member version. Generally, it would work when there were no change in the serialized form of pipeline. Now, Hazelcast fails earlier in this case. #22224
• Removed the BETA annotations from the compact serialization and GenericRecord related classes, i.e., they are stable. Now, compact serialization is enabled by default; the enabled attribute within the compact-serialization configuration block does not exist anymore. #21997

Enhancements

Performance

• MapStore Offloading: Added offload element to map store configuration. It is used to offload map store and loader operations for each map in the cluster. This way, a map store operation does not block the next operations by blocking a partition thread indefinitely. Partition threads are one of the most important shared resources in a cluster; this offloading enables faster completion of the operations in these threads. See Offloading MapStore and MapLoader Operations. #21651

SQL Engine

• Multiple performance enhancements in the SQL engine.

Distribution

• Removed hazelcast-hibernate53 dependency from the main Hazelcast Platform distribution as it is not needed anymore. #22282
• Minor versions of Hazelcast Platform are now released as X.Y.0, instead of the previous X.Y versioning scheme. #22218

Serialization

... (truncated)

Commits

• ebe76d3 Upgrade version to 5.2.1
• 531032a Update release_notes.txt
• eccbbbd Send response to remove offload state (#22756)
• c87b781 Convert HotRestartTriggerBackupMessageTask and ShutdownClusterMessageTask to ...
• 1b50631 Update release_notes.txt
• 1bbb657 Prepare release 5.2.1
• ae612d4 Improve isTechnicalCancellationException check [HZ-1698] [5.2.z] (#22693)
• 324e579 No offload for WB store ops (#22646)
• 3d17706 Update woodstox-core to 6.4.0 [5.2.z] (#22705)
• 66053c5 Avoid logging errors for metricsJournal reads with a wrong sequence [MC-1177]...
• 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)

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 1 day

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.