Officially support dual-stack in downstream clusters

Edge 3.4 will give dual-stack deployments GA status, change the notes
and warnings so that only single-stack IPv6 is not yet officially
supported.

Signed-off-by: Marco Chiappero <[email protected]>
(cherry picked from commit 37e3522)

Author: mchiappero

asciidoc/product/atip-automated-provision.adoc

@@ -748,7 +748,7 @@ spec:
 
 [IMPORTANT]
 ====
-IPv6 and dual-stack deployments are in tech preview status and are not officially supported.
+Single-stack IPv6 deployments are in tech preview status and not yet officially supported.
 ====
 
 The `Metal3Cluster` object specifies the control-plane endpoint (replacing the `$\{DOWNSTREAM_CONTROL_PLANE_IP\}`) to be configured and the `noCloudProvider` because a bare-metal node is used.
@@ -972,7 +972,7 @@ Where:
 [NOTE]
 ====
 * If no network configuration for the host has been specified, either at image build time or through the `BareMetalHost` definition, an autoconfiguration mechanism (DHCP, DHCPv6, SLAAC) will be used. For more details or complex configurations, check the xref:advanced-network-configuration[].
-* Multi-node dual-stack or IPv6 only clusters are not yet supported.
+* Single-stack IPv6 clusters are in tech preview status and not yet officially supported.
 * Architecture must be either `x86_64` or `aarch64`, depending on the architecture of the bare-metal host to be enrolled.
 ====
 
@@ -1529,7 +1529,7 @@ As for the previous example, replace the following variables with actual values,
 
 [IMPORTANT]
 ====
-IPv6 and dual-stack deployments are in tech preview status and are not officially supported.
+Single-stack IPv6 deployments are in tech preview status and not yet officially supported.
 ====
 
 [NOTE]