Address common Zephyr issues to enhance user experience

[bjarki-andreasen]

Enhancing user experience
There are common errors and missing features which are hurting the users experience. Some of these missing features also block Zephyr development and may impede Zephyr adoption, by missing documentation.

The common Zephyr issues
The following common issues are user needs which need to be addressed to enhance the user experience:

• User Need - easily find which features are supported on each board #51722
• User Need - Clear configuration error messages #51723
• User Need - Easily identify APIs supported by device driver #51724

These user needs, which are currently not met:

• Cause obscure errors when building Zephyr, resulting in downtime.
• Prevent automatic documentation, forcing users to look through source code, where they may find non-standardized documentation
• Prevent Zephyr development, by missing metadata that can be used across the build system
• Slow down Zephyr development, by missing metadata that can be used to determine the impact of a change to the code base, which can help testing, CI, identifying relevant reviewers, etc.

Defining the solution(s) requirements
The first step to discover and determine the best solution could be to define the requirements for the solution. Here are some initial requirements:

• The solution(s) should favor automated solutions based on metadata as opposed to manual solutions based on rules.
• The solution(s) should favor handling issues before compilation
• The solution(s) should present solutions to an error, to the user, if an error occurs

Please comment requirements and they will be added here. All requirements are of course up for debate and can be removed/changed.

[mbolivar-nordic]

Arch WG: postponed due to @bjarki-trackunit absence

[nordicjm]

@kartben possibly interested in this?