[Feature]: Allow specific annotation to be set on dgcm-exporter pod's daemonset

[MadJlzz]

Description

Add support to set extra annotations to dcgm-exporter only.
Solves #2271

Checklist

• No secrets, sensitive information, or unrelated changes
• Lint checks passing (make lint)
• Generated assets in-sync (make validate-generated-assets)
• Go mod artifacts in-sync (make validate-modules)
• Test cases are added for new code paths

Testing

Added multiple units tests for now:

• add annotations on dcgm-exporter when daemonsets.annotations is empty
• combine annotations of dcgm-exporter and daemonsets.annotations when both are set

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[MadJlzz]

Hello there maintainers 👋🏼

This is a naive approach to add extra annotations to dcgm-exporter daemonset as well as it's pod. I have nothing against reviewing the entire logic - this is my first time touching a Kubernetes operator.