Provide a machine readable releases.json with EOL dates

Nobody has claimed this yet.

### Describe the bug

I want to automatically check in my CI if the referenced WindowsAppSDK version is still supported.

Please add something like this for AppSDK.

requirements:

- machine readable (json)
- example structure:

```
{
"releases":
[
{
"version": "1.5.1",
"build-version": "1.5.240311000",
"release-version": "1.5", // just guessing the name here
"release-date": "2024-03-12",
"eol-date": "2025-02-28",
"download-urls": [ // stretch goal
{"arch": "x64", "url": "https://aka.ms/windowsappsdk/1.5/1.5.240311000/windowsappruntimeinstall-x64.exe"},
{"arch": "x86", "url": "https://aka.ms/windowsappsdk/1.5/1.5.240311000/windowsappruntimeinstall-x86.exe"},
{"arch": "arm64", "url": "https://aka.ms/windowsappsdk/1.5/1.5.240311000/windowsappruntimeinstall-arm64.exe"},
]
}
]
}
```

DotnetSDK offers a nice orientation, on how it could look:

- https://github.com/dotnet/core/blob/main/release-notes/releases-index.json
- https://github.com/dotnet/core/blob/main/release-notes/8.0/releases.json

Currently, the only way is the non machine readable page: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/release-channels?source=recommendations#release-lifecycle

Start by comparing the proposed structure with dotnet/core's release-notes/releases-index.json and 8.0/releases.json, then review the Windows App SDK release-channels page as the current source for lifecycle dates. Done means adding a maintained machine-readable releases.json containing the requested version, build, release, date, and EOL fields; download URLs are a stretch goal.

Written by the indexing model from the issue text.