[BUG] MicrosoftEdgeUpdate.exe runs in containers by default

[Jamie0]

Description
When using Windows Containers [on AKS], the default base images run the Microsoft Edge installer/updater shortly after a container starts up.

Steps To Reproduce

1. Deploy a new Pod
2. Run kubectl exec -it [pod] -- tasklist (or run ps from a privileged PowerShell, or open Task Manager on the host machine via Baston, etc.)
3. Observe MicrosoftEdgeUpdate.exe runs, starts TrustedInstaller, and installs MS Edge.

Expected Behavior
MicrosoftEdgeUpdate should either not be launched by default, or a documented mechanism should be provided to disable this behaviour.

Environment:

• K8s version: v1.25.6
• containerd version: 1.6.14+azure

More context
We used to work around this by having the Dockerfile disable the associated scheduled task and Windows service, but it appears with a recent update this no longer works. I think the installer script is running within the pause container. I can't imagine that many workloads on AKS require Edge so I would ask the default behaviour is changed to not install it.

After e.g. rebooting a node, the CPU penalty from the Edge installer running in 10-20 pods pushes the node up to 100% CPU utilisation.