Feature: Consider baking mcr.microsoft.com/windows/server:ltsc2022 into Windows AKS base image

**Is your feature request related to a problem?/Why is this needed**
We run a set of containers based off of `server:ltsc2022` due to various dependencies missing in `servercore:ltsc2022`.

When a new node bootstraps, it can take up to 10-15 minutes to pull this image from mcr.microsoft.com

This also has an impact on node pool upgrades, where the backplane doesn't wait for containers to finish pulling images, before proceeding to upgrade the next node. Even if the new node is marked with a NoSchedule taint, this can cause an outage.

**Describe the solution you'd like in detail**
It would be great for `server:ltsc2022` to be baked into the AKS base image, like nanoserver + servercore, to avoid this heavy dependency when a node bootstraps.

This change would for sure increase the image size of the VM image, but I don't think it would have much of an impact on provisioning speed in the grand scheme. I think virtually all OS disks in Azure would have plenty of space capacity for this.

**Describe alternatives you've considered**
We've considered trying to make our application run on plain `servercore`, but we have too many dependencies (e.g. MediaFoundation)

**Additional context**

I opened [an issue](https://github.com/Azure/AKS/issues/4047) related to the upgrade issue, but it was closed for being stale (despite me bumping the issue, albeit a bit late)

Our cloud-based application shares lots of common code with a .NET 4.8 desktop application. We also depend on MediaFoundation which isn't available in servercore. There are many other applications and use cases where servercore isn't sufficient - for example, software that automates/tests web browsers.