Misleading error for deprecated stack versions in Functions

### Describe the bug

The error message provided when attempting to create a function app is inaccurate and misleading. It should be updated to provide a true statement.

### Related command

`az functionapp create`

### Errors

> dotnet-isolated has reached EOL on 2024-11-12 and is no longer supported. https://azure.microsoft.com/en-us/updates/dotnet6support/

### Issue script & Debug output

```cli
az group create -n $groupName -l $location -o none
az storage account create --sku Standard_LRS -l $location -g $groupName -n $storageName --kind StorageV2 -o none
az functionapp create -g $groupName -n $appName -s $storageName --consumption-plan-location $location --functions-version 4 --runtime dotnet-isolated --runtime-version 6
```

### Expected behavior

The issue is that the above message implies that support has ended for the stack ("dotnet-isolated") and not the specific version of the stack (here, .NET 6). Newer versions like .NET 9 are of course perfectly fine to pick at the time of this issue being opened.

Instead, the CLI should specify that the given version has reached end of support. The support state should also be spelled out (not using an acronym) and use active voice. There should also be a call to action. I would expect something more like:

> Support ended for version "6" of stack "dotnet-isolated" on 2024-11-12. Please use a supported version instead. For additional information, see https://azure.microsoft.com/en-us/updates/dotnet6support/.

### Environment Summary

azure-cli 2.67.0

core 2.67.0
telemetry 1.1.0

Extensions:
resource-graph 2.1.0

Dependencies:
msal 1.31.0
azure-mgmt-resource 23.1.1

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\mahender\.azure\cliextensions'

Python (Windows) 3.12.7 (tags/v3.12.7:0b05ead, Oct 1 2024, 02:44:45) [MSC v.1941 32 bit (Intel)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

### Additional context

It stands out to me that the link provided in the error message is for the Web Apps end-of-support announcement. It's valid to point at that, but it makes me think that the behavior here is at least partially being driven by the App Service commands. The link itself does not show up in the Stacks API, and I haven't looked to see if it is somehow constructed in the CLI, but I suspect that's where it comes from.