feat: toggle log severity using rules config

[yufeih]

Enables toggle log severity based on log code in docfx.json using rules such as:

{
  "rules": {
    "InvalidAssemblyReference": "info"
  }
}

Adds the following error code for metadata command:

• InvalidAssemblyReference
• InvalidCref
• InvalidXmlComment
• CodeNotFound

This does not fix #9459 but provides a way to suppress warnings no per error code.

[codecov]

Codecov Report

Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (2ba0c48) 71.34% compared to head (16359dd) 71.34%.

Files	Patch %	Lines
src/Docfx.Common/Loggers/Logger.cs	0.00%	1 Missing and 1 partial ⚠️
src/Docfx.Dotnet/DotnetApiCatalog.cs	0.00%	1 Missing ⚠️
.../ManagedReference/Visitors/SymbolVisitorAdapter.cs	0.00%	1 Missing ⚠️
src/Docfx.Dotnet/Parsers/XmlComment.cs	50.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9460   +/-   ##
=======================================
  Coverage   71.34%   71.34%           
=======================================
  Files         561      561           
  Lines       23980    23987    +7     
  Branches     4170     4173    +3     
=======================================
+ Hits        17108    17113    +5     
- Misses       5778     5779    +1     
- Partials     1094     1095    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bitbonk]

@yufeih Did you ever consider a way to identify and then ignore docfx warnings individually?
Like I can with the CS0000 compiler warnings or with the Diagnostics ID in some Attributes and Roslyn analyzers?

[yufeih]

Let's see if I understand your question: this change would allow individual warnings to be ignored at the error code level, similar to CS0000/Diagnostics ID (although not all warnings/errors have a code today). Are you looking for suppressing levels at an even more granular level such as #pragma warning disable?

[bitbonk]

I think as a first step it would be cool if all warnings/errors that docfx can produce would have an ID and the severity of that warning can be configure globally for a build (e.g. in docfx.json).

Being able to do control the warnings occurrences individually similar to #pragma warning disable might be nice to have, but I suppose that poses the question where one would write down that #pragma warning disable, not all warnings can be associated with a location in a markdown file.

[yufeih]

That make sense and is exactly what this PR is aiming for.