cmake:replenish flatbuffers system/gprof app CMake build

[xuxin930]

Summary

Added flatbuffers cmake scripts
Added system/gprof cmake scripts

Impact

No impact on the past

Testing

ci build

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR does not meet the NuttX requirements.

Here's why and how to improve it:

• Insufficient Summary:
  • Missing "Why": The summary lacks a clear explanation of why these changes are necessary. Are these new features being added? Are existing functionalities being improved? What problems do these additions solve?
  • Missing Details:
    • "Added flatbuffers cmake scripts" is too vague. Which components utilize flatbuffers? How are these scripts integrated?
    • Similarly, specify which parts of the system use gprof and how the new CMake scripts are incorporated.
• Incomplete Impact Assessment:
  • "No impact on the past" is not a valid assessment. While the changes might not directly break existing code, consider potential side effects:
    • Build System: Do these new CMake scripts introduce new dependencies or change the build process for other components?
    • Configuration: Do users need to be aware of any new configuration options or settings related to flatbuffers or gprof?
• Insufficient Testing Information:
  • "ci build" is not descriptive enough. Specify:
    • Host Details: Which CI platforms and configurations were used (OS, compiler versions)?
    • Target Details: On which architectures and boards were the builds tested?
  • Missing Logs: Provide snippets of relevant log output demonstrating the successful integration of flatbuffers and gprof.

To improve this PR:

1. Expand the Summary: Clearly articulate the motivation behind these additions. Provide specific details about what has been changed and how.
2. Thoroughly Assess Impact: Systematically analyze the potential impact on users, the build process, hardware, documentation, security, and compatibility.
3. Provide Detailed Testing Information: Include specific details about your testing environment (both host and target) and share relevant log excerpts showcasing the successful integration and functionality of your changes.