Update documentation for system.process.memory fields to include clarification on Windows memory terminology

[narph]

What does this PR do?

Updates the description of the system/process memory fields.

Why is it important?

Related to #8345
Windows users are confused about the values reflected in the system.process.memory.rss.bytes and system.process.memory.size since the description and naming are not clear enough on the type of memory used/allocated etc.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Relates Improve collection of process memory metrics in Windows #8345

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[blakerouse]

Maybe it would be better detailed description to add this for each supported OS? This way makes it seem like information for Linux or Mac is just missing.

Maybe just on On Windows, this because On Windows os's seems weird as Windows is generally used to represent all versions of Windows as an overall type.

[narph]

@blakerouse ,

Maybe it would be better detailed description to add this for each supported OS? This way makes it seem like information for Linux or Mac is just missing.

I think users will read it as .. This is what this metric represents but on Windows it means the following... So not missing information but an added clarification on the Windows side.

Maybe just on On Windows, this because On Windows os's seems weird as Windows is generally used to represent all versions of Windows as an overall type.

Agree.