{bp-2921} apps: migrate to SPDX identifier

[jerpelea]

Summary

Most tools used for compliance and SBOM generation use SPDX identifiers
This change brings us a step closer to an easy SBOM generation.

included
#2875
#2877
#2879
#2886
#2882
#2891
#2897
#2909
#2911
#2920
#2921

Impact

RELEASE

Testing

CI

[nuttxpr]

[Experimental Bot, please feedback here]

Fill In The Commit Message: This PR contains a Commit with an Empty Commit Message. Please fill in the Commit Message with the PR Summary.

This PR summary is missing crucial information. While it mentions SPDX identifiers and SBOM generation, it doesn't explain what code changes were made. The summary needs to describe the how – what files were modified and what the modifications do. Linking to other PRs is helpful context, but not a substitute for describing the changes within this PR.

Here's a breakdown of the issues and how to fix them:

• Summary: Insufficient detail. Instead of just saying "This change brings us a step closer," explain how. For example: "This PR adds SPDX license identifiers to the license headers of files in the [specify directories/files] directory. These identifiers will enable automated tools to generate a Software Bill of Materials (SBOM)." Mention the specific license(s) added.

• Impact: Saying "RELEASE" is not descriptive. While it might imply a change to the release process or versioning, it's ambiguous. Address each impact point individually and thoroughly. For example:

  • Is new feature added? Is existing feature changed?: YES, Added support for SPDX license identifiers to facilitate SBOM generation.
  • Impact on user: NO (unless there's a user-facing change related to how licenses are displayed or accessed)
  • Impact on build: NO (unless adding the identifiers changes the build process in some way)
  • Impact on hardware: NO
  • Impact on documentation: YES (Documentation should be updated to explain how the SPDX identifiers are used and how to generate an SBOM)
  • Impact on security: Potentially YES. Using standardized license identifiers can help in identifying and mitigating security risks associated with known vulnerabilities in specific open-source components. Explain further.
  • Impact on compatibility: NO (unless there's a specific reason why adding identifiers could break compatibility)
  • Anything else to consider?: Mention any potential issues or considerations related to the SBOM generation process.

• Testing: Saying "CI" isn't sufficient. While CI testing is important, it needs more context. Specify which CI systems were used and what tests were run. Ideally, provide a summary of the test results. If the related nuttx-apps PRs have relevant test logs, link to them specifically. Don't just assume the reviewer will go through all of them. Since this likely impacts a large number of files, it's helpful to show examples of the changes and how they were tested. A "before" and "after" example would be extremely beneficial.

In short, rewrite the PR description to provide specific details about the changes, their impact, and how they were tested. Don't rely on linked PRs to provide all the necessary information. The PR description should be self-contained and easily understood.

[jerpelea]

@xiaoxiang781216 please ignore nxstyle errors

[jerpelea]

CI fixed by apache/nuttx#15386