[nr-k8s-otel-collector] Add DaemonSet and Deployment container port configuration options

[bpschmitt]

Is this a new chart

No

What this PR does / why we need it:

Adds the ability for users to specify what container ports need to be open for both the DaemonSet and Deployment. For example, if a user wants to collect OTel internal telemetry, port 8888 needs to be open.

Which issue this PR fixes

N/A

Special notes for your reviewer:

Checklist

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

• Chart Version bumped
• Variables are documented in the README.md
• Title of the PR starts with chart name (e.g. [mychartname])

Release Notes to Publish

🚀 What's Changed

• Adds the ability for users to specify what container ports need to be open for both the DaemonSet and Deployment. For example, if a user wants to collect OTel internal telemetry, port 8888 needs to be open.

[dbudziwojskiNR]

servicePort is being ignored by the tpl function. Do we need to support this parameter?

[bpschmitt]

@dbudziwojskiNR we should probably adopt what the OTel Collector chart is doing.

https://github.com/open-telemetry/opentelemetry-helm-charts/blob/38fb9903a04c1578f3ec498708e22dcf29510926/charts/opentelemetry-collector/values.yaml#L306-L353

The servicePort just gets added to the associated service for the OTel Collector from what I can tell.

https://github.com/open-telemetry/opentelemetry-helm-charts/blob/38fb9903a04c1578f3ec498708e22dcf29510926/charts/opentelemetry-collector/templates/_config.tpl#L305-L322