Update messaging to be platform-agnostic for WaitAsync availability

Co-authored-by: stephentoub <2642209+stephentoub@users.noreply.github.com>

Author: Copilot

src/Microsoft.CodeAnalysis.NetAnalyzers/src/Microsoft.CodeAnalysis.NetAnalyzers.md

@@ -2166,9 +2166,9 @@ JsonDocument implements IDisposable and needs to be properly disposed. When only
 |CodeFix|True|
 ---
 
-## [CA2027](https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2027): Use Task.WaitAsync instead of Task.WhenAny with Task.Delay
+## [CA2027](https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2027): Cancel Task.Delay after Task.WhenAny completes
 
-When Task.Delay is used with Task.WhenAny to implement a timeout, the timer created by Task.Delay continues to run even after WhenAny completes, wasting resources. Use Task.WaitAsync, which has built-in timeout support without leaving timers running. For frameworks that do not support Task.WaitAsync, pass a CancellationToken to Task.Delay that can be canceled when the operation completes.
+When Task.Delay is used with Task.WhenAny to implement a timeout, the timer created by Task.Delay continues to run even after WhenAny completes, wasting resources. If your target framework supports Task.WaitAsync, use that instead as it has built-in timeout support without leaving timers running. Otherwise, pass a CancellationToken to Task.Delay that can be canceled when the operation completes.
 
 |Item|Value|
 |-|-|

src/Microsoft.CodeAnalysis.NetAnalyzers/src/Microsoft.CodeAnalysis.NetAnalyzers.sarif

@@ -3872,8 +3872,8 @@
         },
         "CA2027": {
           "id": "CA2027",
-          "shortDescription": "Use Task.WaitAsync instead of Task.WhenAny with Task.Delay",
-          "fullDescription": "When Task.Delay is used with Task.WhenAny to implement a timeout, the timer created by Task.Delay continues to run even after WhenAny completes, wasting resources. Use Task.WaitAsync, which has built-in timeout support without leaving timers running. For frameworks that do not support Task.WaitAsync, pass a CancellationToken to Task.Delay that can be canceled when the operation completes.",
+          "shortDescription": "Cancel Task.Delay after Task.WhenAny completes",
+          "fullDescription": "When Task.Delay is used with Task.WhenAny to implement a timeout, the timer created by Task.Delay continues to run even after WhenAny completes, wasting resources. If your target framework supports Task.WaitAsync, use that instead as it has built-in timeout support without leaving timers running. Otherwise, pass a CancellationToken to Task.Delay that can be canceled when the operation completes.",
           "defaultLevel": "note",
           "helpUri": "https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2027",
           "properties": {

src/Microsoft.CodeAnalysis.NetAnalyzers/src/Microsoft.CodeAnalysis.NetAnalyzers/Microsoft.NetCore.Analyzers/MicrosoftNetCoreAnalyzersResources.resx

@@ -1635,13 +1635,13 @@
     <value>Replace 'WhenAll' call with argument</value>
   </data>
   <data name="DoNotUseNonCancelableTaskDelayWithWhenAnyTitle" xml:space="preserve">
-    <value>Use Task.WaitAsync instead of Task.WhenAny with Task.Delay</value>
+    <value>Cancel Task.Delay after Task.WhenAny completes</value>
   </data>
   <data name="DoNotUseNonCancelableTaskDelayWithWhenAnyMessage" xml:space="preserve">
     <value>Using Task.WhenAny with Task.Delay may result in a timer continuing to run after the operation completes, wasting resources</value>
   </data>
   <data name="DoNotUseNonCancelableTaskDelayWithWhenAnyDescription" xml:space="preserve">
-    <value>When Task.Delay is used with Task.WhenAny to implement a timeout, the timer created by Task.Delay continues to run even after WhenAny completes, wasting resources. Use Task.WaitAsync, which has built-in timeout support without leaving timers running. For frameworks that do not support Task.WaitAsync, pass a CancellationToken to Task.Delay that can be canceled when the operation completes.</value>
+    <value>When Task.Delay is used with Task.WhenAny to implement a timeout, the timer created by Task.Delay continues to run even after WhenAny completes, wasting resources. If your target framework supports Task.WaitAsync, use that instead as it has built-in timeout support without leaving timers running. Otherwise, pass a CancellationToken to Task.Delay that can be canceled when the operation completes.</value>
   </data>
   <data name="UseStringEqualsOverStringCompareCodeFixTitle" xml:space="preserve">
     <value>Use 'string.Equals'</value>