User Need - easily find which features are supported on each board

[gregshue]

NOTE: This issue is generated as an action item from the 2022 Oct 27 Dev Review meeting. This issue is to capture/align on the problem statements resulting from #50788.

Is your enhancement proposal related to a problem? Please describe.

As a product prototype developer,
I need to easily and quickly determine which features are supported on a specific board,
so that I can efficiently decide which board to purchase and use for my prototype.

Additional context
This need comes from the Dev Review 2022 Oct 27 minutes, bullet point "Documenting which drivers and features are supported on each board is a manual and error-prone process".

[carlescufi]

Architecture WG:

• @nashif mentions that one option is for the board metadata to be "offline", i.e. metadata that is gathered regularly but not as part of the build system, and is kept in a "database" that is not connected to the actual configuration/build process
  • An example of this approach is something like this: scripts: Scripts to build a relational database #52377
• Kconfig-based approach: RFC: Parse Kconfig to get driver API/feature info #50724
  • This requires running edtlib on each board

[kartben]

I am tempted to call victory on that one :)
I guess it can remain open until a majority of / all boards docs have adopted .. zephyr:board-supported-hw directive

[kartben]

calling victory now that we have almost 600 boards (out of 760) using the .. zephyr:board-supported-hw:: ...