[chore] keep hook annotations for crds installed from upstream operator chart

[jinja2]

Description:

Keep hook annotations to unblock helm upgrades for existing operator installations using upstream installations.
In a previous commit we removed these annotations but see upgrades fail. On upgrade helm sees the object exists but it is not part of tracked objects in its release and throws below error

Error: UPGRADE FAILED: Unable to continue with update: Instrumentation "sock-splunk-otel-collector" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "sock"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"

The alternative is to ask users to add below annotations to instrumentation objects which were created as hook to add them to helm release

meta.helm.sh/release-name
meta.helm.sh/release-namespace

OR ask users to delete the instrumentation object created by hook and let upgrade create a new one.

Link to Splunk idea: <Link to Splunk idea, see https://ideas.splunk.com>

Testing:

Documentation:

[jvoravong]

Just to share. We would need many of the template changes from #1586. Happy to chat as needed.