[k8s] Stabilize k8s resource/entity attributes

[ChrsMark]

Part of https://github.com/open-telemetry/semantic-conventions/issues/3119.

This issue suggests that we stabilise all resource/entity attributes that are used by the following Collector components:

• k8sattributes processor (from metadata.yaml and extract::metadata)
• resourcedetection processor
• filelog receiver

Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/44130.

Suggested Semantic Conventions

Attribute	k8sattributes	resourcedetection	filelog	completion status	semconv link	PR
k8s.pod.name	✅	🚫	✅		link
container.id	✅
container.image.name	✅
container.image.repo_digests	✅
container.image.tag	✅
k8s.cluster.uid	✅				link
k8s.container.name	✅		✅		link
k8s.cronjob.name	✅
k8s.cronjob.uid	✅
k8s.daemonset.name	✅
k8s.daemonset.uid	✅
k8s.deployment.name	✅
k8s.deployment.uid	✅
k8s.job.name	✅
k8s.job.uid	✅
k8s.namespace.name	✅		✅
k8s.node.name	✅
k8s.node.uid	✅
k8s.pod.hostname	✅
k8s.pod.ip	✅
k8s.pod.start_time	✅
k8s.pod.uid	✅		✅
k8s.replicaset.name	✅
k8s.replicaset.uid	✅
k8s.statefulset.name	✅
k8s.statefulset.uid	✅
k8s.container.restart_count			✅
service.instance.id	✅			done	link
service.name	✅			done	link
service.namespace	✅			done	link
service.version	✅			done	link

/cc @open-telemetry/semconv-k8s-approvers @dashpole