libc/lib_utsname: Store version number for debugging and preventing optimization

[W-M-R]

Summary

1. In order to directly read the version information of the current file from elf or bin files, memory files, etc., for easy debugging and one-to-one correspondence.

Impact

None

Testing

None

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR does not meet the NuttX requirements.

Missing Information:

• Summary:

  • Lacks specifics about the change. What functional part of the code is being modified? How does the change work?
  • No mention of related issues or pull requests.

• Impact:

  • The impact section claims "None" across the board. This is highly unlikely for any code change. Every change has some impact. Be specific.
  • Consider:
    • Does this change add new functions or data structures?
    • Does it modify existing code paths?
    • Are there potential performance implications?

• Testing:

  • "None" is unacceptable. Every PR needs evidence of testing.
  • Provide details about your build host(s) and target(s) as specified in the requirements.
  • Include relevant testing logs demonstrating the issue before the change and the correct behavior after.

Recommendations:

1. Elaborate on the Summary: Clearly describe the technical details of your changes.
2. Analyze the Impact: Thoroughly assess and document the impact of your changes, even if they seem minor.
3. Provide Testing Evidence: Demonstrate that your changes work as intended with specific testing details and logs.

A well-documented PR makes it easier for maintainers to understand, review, and merge your contribution.

[acassis]

@W-M-R please copy the comment from Summary to the commit log message

[W-M-R]

@W-M-R please copy the comment from Summary to the commit log message

OK