Publish `apis/<version>` tags on release for the new API submodule

[ialidzhikov]

Component(s)

No response

Is your feature request related to a problem? Please describe.

#5077 introduces a new API submodule.
In order to be able to use a human-readable semver version for this module when another project imports it, a apis/<version> tag should exist.

Currently, the API submodule is imported such as:

require (
	github.com/open-telemetry/opentelemetry-operator/apis v0.0.0-20260529170351-c1218ee73305
)

The target import should be such as:

require (
	github.com/open-telemetry/opentelemetry-operator/apis v1.153.0
)

In order to support the latter, apis/<version> tags should be published on release.

See how other projects with similar API submodules handle it:

• github.com/VictoriaMetrics/operator/api -> tags
• github.com/gardener/etcd-druid/api -> tags
• ...

Describe the solution you'd like

Github Actions to be adapted so that apis/<version> tags to be published on release.

Describe alternatives you've considered

N/A

Additional context

N/A

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[swiatekm]

Yeah, we should do this. I think we thought we didn't have to for some reason, but this was clearly not true. CC @open-telemetry/operator-maintainers