k8seventsreceiver & k8sobjectsreceiver: migrate to latest semconv version

[narcis96]

Description: The version of semconv is upgraded from to v1.6.1 and v1.9.0 to v1.27.0

Link to tracking Issue: #22095

Testing: Tests passed

[TylerHelmuth]

Upgrading semconv is risky. Please confirm that no attributes emitted by this component change bc of this upgrade.

[narcis96]

Upgrading semconv is risky. Please confirm that no attributes emitted by this component change bc of this upgrade.

I confirm that risk is 0. The semconv attributes' value have been compared using go-otel-semconv-comparator resulting in 0 diffs.

[narcis96]

Upgrading semconv is risky. Please confirm that no attributes emitted by this component change bc of this upgrade.

@TylerHelmuth

I used go-otel-semconv-comparator to check that that all constants from the older semconv version have the same value inside the newer semconv version. Thus it is safe to do this upgrade. Check the existing upgrades: #22095

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[narcis96]

did my last reply answered your question ? are there any concerns on this ? @dmitryax @TylerHelmuth @hvaghani221

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[ChrsMark]

Checked were conventions are used:

https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-collector-contrib+path%3Areceiver%2Fk8seventsreceiver+semconv.&type=code&ref=advsearch

https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-collector-contrib+path%3Areceiver%2Fk8sobjectsreceiver+semconv.&type=code&ref=advsearch

It appears it'd be safe to upgrade since k8s.namespace.name and k8s.node.name haven't changed.