github: add specifier to github issue labels

[raiden00pl]

Summary

This change adds a specifier to github labels created with "new issue":

• for labels related to architecture specifier is "Arch: xxx"
• for labels related to issue type specifier is "Type: xxx"
• for labels related to host OS type specifier is "OS: xxx"
• for labels related to issue area type specifier is "Area: xxx"

Impact

with this PR the labels will be more readable and they'll be displayed grouped according to the specifier.
After the PR is merged, the labels in github need to be updated accordingly (label name and color): https://github.com/apache/nuttx/labels

Related issue (doesn't solve it completely): #13522

Testing

tested on private repo and below is the result (https://github.com/raiden00pl/nuttx/issues)

I just chose random colors for the above test

[nuttxpr]

[Experimental Bot, please feedback here]

NuttX PR Requirements Review

Meets Requirements? Partially

Summary: The summary clearly explains the change and its purpose. However, it lacks references to related issues if any.

Impact:

• New Feature: YES
• User Impact: YES - Users will need to adapt to the new label names and organization.
• Build Impact: NO
• Hardware Impact: NO
• Documentation Impact: YES - Documentation should be updated to reflect the new label naming convention.
• Security Impact: NO
• Compatibility Impact: Potentially - Existing workflows or tools relying on the old label names might be affected.

Testing:

• Testing on a private repo is a good start. However, testing on the actual apache/nuttx repository is crucial before merging.
• The "Testing logs" sections are not applicable in this case as the change primarily affects GitHub labels, not code execution. Screenshots demonstrating the label organization are helpful.

Recommendations:

1. Related Issues: Link any related NuttX issues to provide context.
2. Testing: Perform a test run on a fork of the apache/nuttx repository to ensure compatibility.
3. Documentation: Update relevant documentation to reflect the new label structure.
4. Impact on Compatibility: Elaborate on potential compatibility issues with existing workflows.

Overall: The PR addresses a valid need for label organization. Addressing the recommendations will ensure a smoother integration and adoption of this change.

[simbit18]

@raiden00pl now you also need to change the text and color of the labels.

[raiden00pl]

@simbit18 Yes, I'll start working on it once PR is merged or at least it gets some approvals

[simbit18]

Then we need to remember to do the same on the apps repository. :)