Add initial Buildcheck codes

[JanKrivanek]

Contributes to #10240

Context

Customer requested to have understandable documentation of individual imposed rules.
Let's follow similar practice we introduced in template engine - with adding short hyperlinks to the outputs, that can then include rich information, that can freely evolve off-cycle.

Changes Made

Added initial document
Added initial code adding the hyperlink

What remains TBD for the bug (but out of scope of this PR)

• Adding a document for custom codes (that will not have enumeration, but just an overview of what custom analyzer are, how they can appear in your build and how you can understand and troubleshoot the reports)
• Conditionalize the link adding code - so that it uses different link for custom analyzers (this will be easy after [Built-in analyzer] Undefined property is used #9883 is done - as it'll introduce internal overload of the base class, that will be used by built-in analyzers)
• Adding a link to finalized guidelines - once [BuildCheck]: Guide of rules/analyzers id name #10088 is finalized

UX

[maridematte]

Should we wait to merge this after the guidelines are established? Or go for it now and update later.

[JanKrivanek]

Should we wait to merge this after the guidelines are established? Or go for it now and update later.

I'd see it as almost independent.
This is just a basement that we'll build upon

[rainersigwald]

LGTM with Chet's edits