docs: PCP-4752: Updated Breaking Change re: MAAS AZ Node Pool (#7715)

* Updating MAAS node pool breaking change guidance

* ci: auto-formatting prettier issues

* Update docs/docs-content/release-notes/release-notes.md

Co-authored-by: Ben Radstone <[email protected]>

* ci: auto-formatting prettier issues

---------

Co-authored-by: achuribooks <[email protected]>
Co-authored-by: Ben Radstone <[email protected]>

Author: achuribooks

docs/docs-content/release-notes/release-notes.md

@@ -21,11 +21,14 @@ tags: ["release-notes"]
 
 #### Breaking Changes {#breaking-changes-4.7.a}
 
-- Availability zones are now required for MAAS [node pools](../clusters/cluster-management/node-pool.md) when deploying
-  [MAAS clusters](../clusters/data-center/maas/create-manage-maas-clusters.md). Availability zones are _not_ required
-  when performing Day-2 node pool updates on MAAS clusters deployed prior to Palette version 4.7.a. Changing
-  availability zones post-cluster deployment will trigger a
-  [node pool repave](../clusters/cluster-management/node-pool.md#repave-behavior-and-configuration).
+- Availability zones are now required when creating MAAS [node pools](../clusters/cluster-management/node-pool.md).
+  - For [MAAS clusters](../clusters/data-center/maas/create-manage-maas-clusters.md) deployed prior to Palette version
+    4.7.a, selecting an availability zone is required when creating a new node pool; however, selecting an availability
+    zone is _not_ required when modifying an existing node pool, as modifying availability zones post-cluster deployment
+    will trigger a [node pool repave](../clusters/cluster-management/node-pool.md#repave-behavior-and-configuration).
+  - For MAAS clusters deployed prior to 4.7.a, we recommend creating a new node pool with an availability zone selected
+    and migrating existing workloads to the new node pool when convenient. For guidance on migrating workloads, refer to
+    the [Taints and Tolerations](../clusters/cluster-management/taints.md) guide.
 
 #### Features