Backport of Datadog Integration Acceptance Tests / Bug fixes into release/1.3.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #3685 to be assessed for backporting due to the inclusion of the label backport/1.3.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@natemollica-nm
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-k8s/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Changes proposed in this PR

• Introduce datadog integration acceptance testing with Datadog API
  • Consul Integration
  • DogstatsD (Unix Domain Sockets)
  • DogstatsD (UDP)
  • Openmetrics Prometheus
  • OTLP Collection Integration (HTTP)
  • OTLP Collection Integration (gRPC)
• Fix some bugs surrounding the Openmetrics and Consul Integration Checks
  • Consul Checks also require prometheus.io annotations to be removed while enabled to avoid conflicts w/ dd-agent
  • Fix Openmetrics and Consul Integration check URLs to use consul.fullname-server helper template for accurate consul API access
  • Fix OTLP collection for telemetry-collector-deployment.yaml to include OTEL_EXPORTER_OTLP_ENDPOINT env variable for proper Datadog tag ingestion

How I've tested this PR

• Ran: make bats-test for templating updates
• Ran acceptance tests for new Datadog framework and test scenarios following CONTRIBUTING.md guide.

How I expect reviewers to test this PR

• Review acceptance tests and see if they're worth even having in the repository. They add a few more go dependencies for Datadog client API access
  • The tests access the datadog agent's local API with datadog dogstatsd stats enabled to parse metrics output from the collection event.
  • This testing leverages the Datadog fake-intake image to simulate traffic ingestion and remove the requirement to have to use an API and APP key.

Checklist

• Tests added
• CHANGELOG entry added

---

Overview of commits

• 8e09172 - cad42f1 - 61d4b2d - bb068a4 - 8a13734 - e60a939 - 13b7089 - 59dccfd - 7a31b1d - b14f5db - 4233e75 - a49b6cb - 4b1dbc1 - 694e9df - 11f4603 - aa495c4 - 3b4287c - 9e77ced - 401b749 - 51df717 - dee86b1 - e79c6ea - 88e8a65 - de58b99 - 943f4dd - 47eec97 - 0bd8838 - 0f8cd4f - 69c81d7 - 70f7390 - 078c2d0 - 91abb5d - 55f94fa

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}