Documentation: update sensors documentation

[raiden00pl]

Summary

• add info about different sensor frameworks in one place
• fix headers style for sensors_uorb.rst: headers
• fix long lines for sensors_uorb.rst so it's possible to read this file in terminal IDE
• add code sections for sensors_uorb.rst

Impact

fix #11082

Testing

local

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR description does not fully meet the NuttX requirements. While it provides some information, it lacks crucial details in several sections. Here's a breakdown:

Missing/Insufficient Information:

• Summary: While it lists changes, it doesn't explain why these changes are necessary. For example, why is it important to add information about different sensor frameworks in one place? What problem does it solve? What benefit does it provide? Similarly, why were the headers, long lines, and code sections problematic in sensors_uorb.rst? The summary needs to explain the motivation for the changes.
• Impact: While it links to an issue, it doesn't adequately fill out the impact checklist. Even if the changes seem minor, explicitly stating "NO" for each impact category (if applicable) is important for reviewers. If any answer is "YES", a description is required. For example, does this impact documentation? The PR description implies it does, but doesn't explicitly say so or describe the impact.
• Testing: "local" is insufficient. The requirements ask for specifics about the build host and target(s). What OS, architecture, board, and configuration were used? Furthermore, there are no "testing logs before change" and "testing logs after change" provided. Even if the change is primarily documentation, showing the rendered output before and after the change would be helpful.

How to improve this PR description:

1. Expand the Summary: Explain the reasoning behind each change. What problems did the changes address? What benefits do they provide? For instance: "The lack of a centralized overview of sensor frameworks made it difficult for developers to understand the available options and choose the right one. This change consolidates this information to improve developer experience."

2. Complete the Impact Assessment: Go through each impact item and explicitly state "NO" or "YES" with a description if "YES". For example:

   • Impact on documentation: YES. This PR updates the sensors_uorb.rst file to improve clarity and readability by fixing header styles, line lengths, and adding code examples.
   • Impact on user: Potentially YES. If users rely on the sensors_uorb.rst file, this change will improve their experience.

3. Provide Detailed Testing Information: Specify the build host OS, CPU, compiler, and version. Specify the target architecture, board, and configuration. Include relevant testing logs or demonstrate the rendered output before and after the change for documentation updates. Example:

   • Build Host: macOS Ventura, Apple M1 Pro, clang-14
   • Target: sim:qemu-x86_64

By addressing these points, the PR description will meet the NuttX requirements and be much easier for reviewers to understand and approve.