DOC-449 - remove transactions deprecation notice (#1681)

https://hazelcast.atlassian.net/browse/DOC-449

Author: Rob-Hazelcast

docs/modules/clients/pages/java.adoc

@@ -406,12 +406,6 @@ each distributed data structure in this Reference Manual.
 Transactional distributed objects are supported on the client side.
 See xref:transactions:providing-xa-transactions.adoc[Transactions] for more details.
 
-[CAUTION]
-.Deprecation Notice for Transactions
-====
-Transactions have been deprecated, and will be removed as of Hazelcast version 7.0. An improved version of this feature is under consideration. If you are already using transactions, get in touch and share your use case. Your feedback will help us to develop a solution that meets your needs.
-====
-
 === Async Start and Reconnect Modes
 
 Java client can be configured to connect to a cluster in an async manner during the

docs/modules/cluster-performance/pages/pipelining.adoc

@@ -47,12 +47,6 @@ ICache, IAtomicLong, etc. It cannot be used as a transaction mechanism though. S
 none of the requests are executed. If you want to use an atomic behavior, see  xref:transactions:providing-xa-transactions.adoc[Transactions] for more details.
 The pipelining is just a performance optimization, not a mechanism for atomic behavior.
 
-[CAUTION]
-.Deprecation Notice for Transactions
-====
-Transactions have been deprecated, and will be removed as of Hazelcast version 7.0. An improved version of this feature is under consideration. If you are already using transactions, get in touch and share your use case. Your feedback will help us to develop a solution that meets your needs.
-====
-
 The pipelines are cheap and should frequently be replaced because they accumulate results. It is fine to have a few hundred or
 even a few thousand calls being processed with the pipelining. However, all the responses to all requests are stored in the pipeline
 as long as the pipeline is referenced. So if you want to process a huge number of requests, then every few hundred or few

docs/modules/release-notes/pages/5-4-0.adoc

@@ -312,8 +312,6 @@ With this fix, only the members on which the jobs have not been completed are qu
 https://github.com/hazelcast/hazelcast/pull/24734[#24734]
 * The evaluation tool for IMDG 3.x users (Hazelcast 3 Connector) is removed. In the upcoming releases, a new tool for migrating data from 3.x versions will be introduced.
 https://github.com/hazelcast/hazelcast/pull/25051[#25051]
-* Transactions have been deprecated, and will be removed as of Hazelcast version 7.0.
-An improved version of this feature is under consideration. If you are already using transactions, get in touch and share your use case. Your feedback will help us to develop a solution that meets your needs.
 * Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.
 * The user code deployment API is deprecated, and will be removed in Hazelcast Platform version 6.0. #223
 

docs/modules/transactions/pages/creating-a-transaction-interface.adoc

@@ -1,11 +1,5 @@
 = Creating a Transaction Interface
 
-[CAUTION]
-.Deprecation Notice for Transactions
-====
-Transactions have been deprecated, and will be removed as of Hazelcast version 7.0. An improved version of this feature is under consideration. If you are already using transactions, get in touch and share your use case. Your feedback will help us to develop a solution that meets your needs.
-====
-
 You create a `TransactionContext` object to begin, commit and rollback
 a transaction. You can obtain transaction-aware instances of queues,
 maps, sets, lists and multimaps via `TransactionContext`, work with

docs/modules/transactions/pages/providing-xa-transactions.adoc

@@ -1,11 +1,5 @@
 = Providing XA Transactions
 
-[CAUTION]
-.Deprecation Notice for Transactions
-====
-Transactions have been deprecated, and will be removed as of Hazelcast version 7.0. An improved version of this feature is under consideration. If you are already using transactions, get in touch and share your use case. Your feedback will help us to develop a solution that meets your needs.
-====
-
 XA describes the interface between the global transaction manager and the
 local resource manager. XA allows multiple resources (such as databases,
 application servers, message queues and transactional caches) to be accessed