Use build in automatic generated code detection: AnalysisContext.ConfigureGeneratedCodeAnalysis

[costin-zaharia-sonarsource]

Check if we can replace the in-house automatic generated code detection with AnalysisContext.ConfigureGeneratedCodeAnalysis from Roslyn.

According to the documentation:

It is recommended for the analyzer to invoke this API with the required GeneratedCodeAnalysisFlags setting.

• Check if we can achieve the same functional requirements with the Roslyn API.
• Check if there will be any changes in terms of performance.
• Do the actual change.

Arguments for doing this change:

• less code to maintain
• theoretically, the performance should be better since:
  -- the Roslyn checks are most likely run anyway
  -- we do expensive checks on our end and rely on caching to save time, but our caching needs thread synchronization (ConcurrentDictionary) for this to work which might slow down the analysis. Outside IDEs, the rules are executed concurrently.
  -- measurement is needed

[glucaci]

How it the in-house automatic generated code detection working because with [LoggerMessage] is not working.
See #5466.

Thanks!

[costin-zaharia-sonarsource]

Hi @glucaci,

in-house automatic generated code detection, in the current context, does not refer to code generators. It is about detecting if a code file was automatically generated by the visual studio IDE or other frameworks. E.g. designer files from windows forms.

[pavel-mikula-sonarsource]

More context is reported by @RyanThomas73 in #6607

[martin-strecker-sonarsource]

Related: #8298