Removed claimed support for NVMe disk controller for older versions (#59489)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: bonsohi

data/release-notes/enterprise-server/3-14/18.yml

@@ -17,8 +17,6 @@ sections:
   changes:
     - |
       For administrators managing logs, log folders are more consistently accessible from the administrative account without the need to use `sudo`.
-    - |
-      Azure VMs that use the NVMe disk controller are now supported, as well as Azure VMs that do not include temporary resource disks.
   known_issues:
     - |
       During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.

data/release-notes/enterprise-server/3-15/13.yml

@@ -19,8 +19,6 @@ sections:
       For administrators managing logs, log folders are more consistently accessible from the administrative account without the need to use `sudo`.
     - |
       Administrators can no longer run the `ghe-upgrade` command on a replica node if a configuration apply is running or has failed on the primary node. This change helps prevent upgrade conflicts and ensures more reliable high availability maintenance workflows.
-    - |
-      Azure VMs that use the NVMe disk controller are now supported, as well as Azure VMs that do not include temporary resource disks.
     - |
       Administrators monitoring Elasticsearch index repair jobs benefit from improved log clarity. Log messages provide more detailed and actionable information, making it easier to troubleshoot and track the progress of index repair operations.
   known_issues:
@@ -63,4 +61,4 @@ sections:
     - |
       Upgrading to this version from GHES 3.14.19 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.15.14 or higher.
 
-      [Updated: 2025-11-24]
+      [Updated: 2025-11-24]

data/release-notes/enterprise-server/3-16/9.yml

@@ -27,8 +27,6 @@ sections:
       For administrators managing logs, log folders are more consistently accessible from the administrative account without the need to use `sudo`.
     - |
       Administrators can no longer run the `ghe-upgrade` command on a replica node if a configuration apply is running or has failed on the primary node. This change helps prevent upgrade conflicts and ensures more reliable high availability maintenance workflows.
-    - |
-      Azure VMs that use the NVMe disk controller are now supported, as well as Azure VMs that do not include temporary resource disks.
   known_issues:
     - |
       Custom firewall rules are removed during the upgrade process.
@@ -74,4 +72,4 @@ sections:
       Upgrading to this version from GHES 3.14.19 and higher or 3.15.14 and higher will cause the upgrade to fail due to this version containing an older version of MySQL. To avoid this issue please upgrade to GHES 3.16.10 or higher.
 
       [Updated: 2025-11-24]
-      
+