[Windows] Create service utils

[richl-dd]

What does this PR do?

This PR creates a file that exposes utilities to interact with Windows services via the Service Control Manager (SCM). It wraps OpenSCManager and OpenService to allow the caller to specify the desiredAccess rights (as opposed to the Go package that uses ALL_ACCESS). This will allow agent code to use least-privilege accesses when working with Windows services.

Motivation

The motivation is to enable least-privileges SCM interactions from one place in the agent repo.

Additional Notes

• The ListDependentServices function will list first, second, third, ... level dependencies
• It doesn't seem like Go is planning to make this change upstream:
  • x/sys/windows: get Windows services status without all access permissions golang/go#48777
• Some of the test code helper functions are copy/pasted from: go\pkg\mod\golang.org\x\sys@v0.4.0\windows\svc\mgr\mgr_test.go. Assuming this is fine, because in the above issue the answerer suggested copying code directly from the package
• There is an open issue to add enumDependentServices to the Go package, when that is merged, we should update our code to use that function
  • x/sys/windows/svc/mgr: Add EnumDependentServices method to Service struct golang/go#56766

Possible Drawbacks / Trade-offs

• None I was able to identify at this time.

Describe how to test/QA your changes

• There is some coverage in the unit tests:
  • https://github.com/DataDog/datadog-agent/pkg/util/winutil/service_test.go
• The current kitchen tests install and run the agent, so those should be sufficient
• To manually test this, installing the agent should also be sufficient

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.

[iglendd]

I wonder if we have other places in Agent where SCM is used and we probably can switch to this new code.