[k8s] Define semantic conventions for k8s memory metrics

[ChrsMark]

Area(s)

area:k8s

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

As part of the K8s SemConv stability work we need to define k8s memory metrics that are already in use by the Opentelemetry Collector.

Related to #1032.

Describe the solution you'd like

The existing metrics in use that we need to define as semantic conventions are the following:

k8s.node.memory.usage: ✅ #1406
container.memory.usage: ✅ #282
k8s.pod.memory.usage: ✅ #1406
k8s.node.memory.available: #2776
k8s.node.memory.rss: #2776
k8s.node.memory.working_set: #2776
k8s.node.memory.page_faults: #2776
k8s.node.memory.major_page_faults: #2776
k8s.pod.memory.available: #2776
k8s.pod.memory.node.utilization: #2777
k8s.pod.memory_limit_utilization: #2777
k8s.pod.memory_request_utilization: #2777
k8s.pod.memory.rss: #2776
k8s.pod.memory.working_set: #2776
k8s.pod.memory.page_faults: #2776
k8s.pod.memory.major_page_faults: #2776
container.memory.available: #2776
k8s.container.memory_limit_utilization: #2777
k8s.container.memory_request_utilization: #2777
container.memory.rss: #2776
container.memory.working_set: #2776
container.memory.page_faults: #2776
container.memory.major_page_faults: #2776

Additional context

No response

[ChrsMark]

Also related to this one: open-telemetry/opentelemetry-collector-contrib#35849

[ChrsMark]

For *utilization metrics I wonder if we should try defining them or if we should just deprecate them and let users calculate them on their back-ends since there are a lot of discussions around them. An example can be found at open-telemetry/opentelemetry-collector-contrib#40444.