Look into Agent changes for running ADP on Windows.

[tobz]

Currently, we do not build ADP on Windows. As part of doing so, we'll have to consider how to actually use ADP on Windows with the Agent, which means running ADP like any other subagent.

From some internal chats, it seems like this hinges on two main bits of work:

• creating/install a Windows service for ADP
• updating the Core Agent to actually trigger the service start/stop for the ADP service when ADP is enabled

We should investigate further to understand the scope of these items, and if there are any other chunks of work we'll need to do in order to support running ADP on Windows, as the potential of requiring Agent changes means the iteration time of fixing bugs with adding said support becomes much, much higher than just updating the s6 files we bundle in the Linux container image, etc.

[tobz]

Random note: on Windows, we pass a -foreground flag to subagents when running them in Kubernetes (here).. so we should investigate what that flag is actually doing and if that's a specific bit of functionality we need to add to ADP.

[tobz]

Agent subcommand logic that figures out which Windows services to start/stop based on specific configuration values: https://github.com/DataDog/datadog-agent/blob/main/cmd/agent/subcommands/run/dependent_services_windows.go#L32-L73

[tobz]

Example code for how we define and add the Windows services themselves during installation: https://github.com/DataDog/datadog-agent/blob/main/tools/windows/DatadogAgentInstaller/WixSetup/Datadog%20Agent/AgentInstaller.cs#L563