Add Windows Named Pipes to the Trace Agent

[Lewis-E]

What does this PR do?

• Adds a NamedPipe BufferReader option to let the datadog-trace-agent use windows specific functionality
• Mimic existing TCP behavior for the named pipe, using the rust http server Hyper.
• Uses DD_APM_WINDOWS_PIPE_NAME for config + DD_APM_RECEIVER_PORT is overridden to 0 when pipe name is set
• The issue of multiple functions is NOT solved by this PR. We need to add a uniqueness factor to the envvar to handle multiple functions in the same plan, similar to the AAS extension GUID usage, but this needs to be handled 1) at the compat layer so it can be distributed to the rust mini-agent and the dogstatsd library from a single source of truth, and 2) we can't modify envvars in java, so we will also need to add another communication method to dogstatsd java envvar handling.

Motivation

• When multiple functions run in Windows run on the same plan, only one can connect due to port conflicts for trace agent and dogstatsd agent. The Serverless Compatibility Layer should use named pipes in Windows for transport to prevent this issue.

Additional Notes

• See also: Add Windows Named Pipes to Dogstatsd #59

Describe how to test/QA your changes

• Add integration test
• Manual testing in Azure

[duncanpharvey]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[jcstorms1]

General logic looks good to me and similar to the windows extension. I'll defer more technical comments to others with more expertise.

[duncanpharvey]

Following the addition of profiling support, do we need named pipes there as well? Maybe that's something we can handle in a separate PR.

#40

[duncanpharvey]

LGTM! Can you address the merge conflicts that fix the clippy warnings? Then this is good to merge!