Enhancement for Rust build

[no1wudi]

Summary:

• Update the NuttX Rust crate dependency to use the main branch instead of master for consistency with upstream repository changes.
• Fix framebuffer pixel format check by replacing Format::RGB565 with FB_FMT_RGB16_565 to ensure accurate validation of the video format.

nuttx-rs (https://github.com/no1wudi/nuttx-rs) generate binding from NuttX's C header now, which simplify the build setup and get more accurate struct/data type definitions.

Impact:

• New feature added? NO
• Impact on user? NO
• Impact on build? YES - Updates dependency branch in Cargo.toml, affecting crate resolution.
• Impact on hardware? NO
• Impact on documentation? NO
• Impact on security? NO
• Impact on compatibility? NO

This PR ensures compatibility with the latest NuttX Rust crate repository structure and corrects a critical pixel format check for reliable framebuffer handling.

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR generally meets the NuttX requirements, although it's missing some key information in the Testing section. While it describes the changes and their impact well, it needs to provide specific build hosts and targets used for verification, along with actual testing logs. The reference to nuttx-rs seems out of place in the Summary and should probably be part of the description of "how the change exactly works".

Here's a breakdown of what's good and what needs improvement:

Good:

• Clear Summary: Explains the "why" and "what" of the changes.
• Well-Defined Impact: Addresses all impact categories with clear YES/NO answers and explanations where necessary.
• Concise Explanation: Provides a good overview of the benefits of the changes.

Needs Improvement:

• Testing Section: This is the most significant deficiency.
  • Missing Build Hosts: Specify the OS, CPU architecture, and compiler used for local testing. Example: Linux, x86_64, GCC 12.1.0
  • Missing Targets: Specify the target architecture, board, and configuration. Example: sim:qemu-x86_64:nsh
  • Missing Logs: Provide actual logs demonstrating the issue before the change and the corrected behavior after the change. Even simple logs showing successful framebuffer initialization or output would be helpful. Without these logs, it's impossible to verify the claims made in the PR.
• Summary Clarity: Move the nuttx-rs explanation into the "how it works" part of the summary. The current placement makes it seem like a separate change. Rephrase to something like: "This change updates the NuttX Rust crate dependency... and corrects the framebuffer pixel format check... The nuttx-rs crate now generates bindings..."

By providing the missing testing details, this PR will fully meet the NuttX requirements.

[cederom]

Thank you @no1wudi :-)