CAMEL-22041 Deprecate hazelcast-atomicvalue, add hazelcast-pncounter as a replacement, replace use of java.util.concurrent.locks.Lock.

[cunningt]

Description

In Hazelcast 5.5+, the CP subsystem is removed from the community edition, and is only available in the enterprise edition.

It appears like if we move to hazelcast 5.5+, the hazelcast-atomicvalue (atomicnumber) component either needs to be removed or the data structure backing it needs to change - the IAtomicLong it uses is a CP subsystem only feature https://docs.hazelcast.com/hazelcast/5.6/data-structures/iatomiclong .    We can replace most of the functionality with a PNCounter https://docs.hazelcast.com/hazelcast/5.6/data-structures/pn-counter with one limitation - PNCounter does not offer a compare/compareAndSet method.      I think offering a new component here (hazelcast-pncounter) seems like a better approach because it is more descriptive of the underlying data structure used and because we would be removing significant functionality because no compareAndSet is available.

We should deprecate hazelcast-atomicvalue (atomicnumber) in 4.19.0 and create a hazelcast-pncounter to replace it.    We can then safely remove hazelcast-atomicvalue in a future release and safely upgrade to hazelcast 5.5.0 or 5.6.0.

Target

• [ x] I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• [x ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• [x ] I checked that each commit in the pull request has a meaningful subject line and body.

• [x ] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.