[CONTP-719] Expose security context and annotation configurations

[Mathew-Estafanous]

What this PR does / why we need it:

1. Exposes securityContext and annotations as configurable values in the CSI Driver.
2. Adds baseline tests to validate proper formatting of rendered helm charts.

Which issue this PR fixes

The Datadog CSI Driver has limited configuration options and we'd like to expose important security related configuration options for customers deploying the CSI Driver.

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• All commits are signed (see: signing commits)
• Chart Version semver bump label has been added (use <chartName>/minor-version, <chartName>/patch-version, or <chartName>/no-version-bump)
• For datadog or datadog-operator chart or value changes, update the test baselines (run: make update-test-baselines)

GitHub CI takes care of the below, but are still required:

• Documentation has been updated with helm-docs (run: .github/helm-docs.sh)
• CHANGELOG.md has been updated
• Variables are documented in the README.md

[gabedos]

Can you clarify what the purpose of this SkipTest constant is?

I see that the Operator unit tests have it but I also don't understand the purpose of it there:

helm-charts/test/datadog-operator/operator_deployment_test.go

Lines 23 to 35 in c523cc5

	const (
	SkipTest = false
	)
	func Test_operator_chart(t *testing.T) {
	tests := []struct {
	name string
	command common.HelmCommand
	assertions func(t *testing.T, manifest string)
	skipTest bool
	}{
	{

The other unit tests for regular helm chart don't have this const.

[Mathew-Estafanous]

No particular reason besides copying it from the operator tests. I'll remove it.

[gabedos]

Exposing the additional configuration options as well as implementing the unit tests for the datadog-csi-driver helm chart looks good to me!

[Mathew-Estafanous]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-01-23 20:28:43 UTC ℹ️ Start processing command /merge

---

2026-01-23 20:28:52 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 50m (p90).

---

2026-01-23 20:53:46 UTC ℹ️ MergeQueue: This merge request was merged