Rename *.linux.memory to *.memory.linux

[rogercoll]

Fixes #1661

Changes

Please provide a brief description of the changes here.

Important

Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions)

[github-actions]

This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:

• linux

Such changes may be rejected or put on hold until a new SIG/project is established.

Please refer to the Semantic Convention Areas
document to see the current active SIGs and also to learn how to kick start a new one.

[rogercoll]

Reopening because of this PR changes removing any metric/attribute in the Linux area

[github-actions]

This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:

• linux

Such changes may be rejected or put on hold until a new SIG/project is established.

Please refer to the Semantic Convention Areas
document to see the current active SIGs and also to learn how to kick start a new one.

[github-actions]

This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:

• linux

Such changes may be rejected or put on hold until a new SIG/project is established.

Please refer to the Semantic Convention Areas
document to see the current active SIGs and also to learn how to kick start a new one.

[lmolkova]

I think https://github.com/open-telemetry/semantic-conventions/blob/main/docs/non-normative/groups/system/design-philosophy.md#operating-system-in-names talks about root namespace, is there a need or benefit in renaming system.linux.memory.slab.usage to system.memory.linux.slab.usage ?

In the new version, linux looks like a property of memory and separates actual slab.usage property. In the old version it feels in the right place - it's a property of a system.

[rogercoll]

We might need to rephrase it, but I think instead of "root namespace" what we meant is {area}. The way we think a user interacts with system metrics is by first looking into the area of interest (e.g. memory consumption alert) and then (if needed), looking to the OS more fine-grained metrics for that area.

If we just apply the rule to root namespaces, we could end up having a mix of unordered metrics like memory.linux.* and system.linux.memory.*.

cc @braydonk

[lmolkova]

I'm not going to block on this, but I'm still raising concern. It seems random where OS name is included and it affects name readability