[bp-15102} update documentation

[jerpelea]

Summary

this patch includes
#15102
#15121
#15122

Impact

RELEASE

Testing

CI

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR summary does not adequately meet the NuttX requirements. While it references other PRs, it fails to provide the necessary context and details required by the template.

Here's why it's insufficient and how it could be improved:

• Summary: Simply listing PR numbers doesn't explain why these changes are necessary, what they change, or how they work. The summary should be self-contained and describe the overall purpose and functionality of the combined changes.
• Impact: Stating "RELEASE" doesn't provide any specific information. Each impact category (user, build, hardware, documentation, security, compatibility) should be addressed individually with "YES" or "NO" and a description if "YES". For a release, many of these are likely to be "YES" and require explanation.
• Testing: "CI" is insufficient. While CI testing is important, the template requires specific details about the local testing environment (host and target) and logs demonstrating the behavior before and after the change. Relying solely on CI results doesn't offer enough evidence of thorough testing, especially for a release.

How to improve this PR summary:

1. Consolidate the changes: If these three PRs are logically related and meant to be merged together, the ideal approach would be to squash them into a single, well-structured PR. This simplifies review and makes tracking changes easier.

2. Provide a comprehensive summary: Explain the overall goal of the combined changes. What problem are they solving, or what new functionality are they introducing? Briefly describe the core modifications made in each of the original PRs within this unified summary.

3. Detail the impact: Go through each impact category and specify "YES" or "NO". For each "YES," provide a concise description of the impact. For a release, this is especially crucial. Consider areas like API changes, configuration updates, or deprecated features.

4. Provide testing details: List the specific host and target environments used for testing. Include relevant logs demonstrating the behavior before and after the change. This validates the functionality and helps reviewers assess the effectiveness of the testing process. Don't just rely on CI.

By addressing these points, the PR summary will provide the necessary information for reviewers to understand the changes and assess their impact effectively, ultimately leading to a smoother and more efficient review process.