adding health check in to health checkv2

[badal773]

Description:
Add support for healthcheckv2 extension in the OpenTelemetry Operator to enable automatic liveness, readiness, and startup probe generation.

Link to tracking Issue(s):

• Resolves: [opentelemetry-kube-stack] LivenssProbe not showing up on collector pods, even it is set in values.yaml of kube-stack helm chart and operator creates daemonSet opentelemetry-helm-charts#1996

Testing:

Documentation:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: badal773 / name: Badal Kumar (8646445)

[github-actions]

E2E Test Results

 34 files  ±0  227 suites  ±0   2h 40m 32s ⏱️ + 36m 25s
 90 tests ±0   86 ✅  - 4  0 💤 ±0  4 ❌ +4 
231 runs  ±0  227 ✅  - 4  0 💤 ±0  4 ❌ +4 

For more details on these failures, see this check.

Results for commit 8646445. ± Comparison against base commit 915d7c2.

[iblancasa]

You can just use v2 from v1 enabling a feature gate https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/healthcheckextension#feature-gate-extensionhealthcheckusecomponentstatus

healthcheckv2 will be removed at some point

[swiatekm]

You can just use v2 from v1 enabling a feature gate https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/healthcheckextension#feature-gate-extensionhealthcheckusecomponentstatus

healthcheckv2 will be removed at some point

I don't think this is necessarily a blocker. It'll take a while before that feature gate is enabled by default and healthcheckv2 is deprecated. Looking at this PR, it doesn't cost us much to support it. @open-telemetry/operator-approvers opinions?