Update `.globalconfig` rules

[xtqqczze]

We should compare our .globalconfig with recommended .globalconfig from latest NetAnalyzers package.

[xtqqczze]

To follow latest .globalconfig from .Net SDK we have to remove our custom one and migrate our configs to .editorconfig

@iSazonov I do not understand why this is necessary.

[iSazonov]

See docs https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/overview?tabs=net-9

Analyzers run by default now and use default config file from installed .Net SDK (with latest rules) based on AnalysisMode option. So now we have no need to copy .globalconfig to our repository - all rules we need we can configure in our .editorconfig file. Also we can force more rules with Recommended option.

So our plan should be:

1. Migrate Settings.StyleCop rules to .editorconfig and remove Settings.StyleCop
2. Migrate rules (we modified previously) from our .globalconfig to .editorconfig and remove .globalconfig

Code analysis in .NET

Learn about source code analysis in the .NET SDK.

[xtqqczze]

According to code analysis documentation, we can use either:

• EditorConfig file
• Global AnalyzerConfig file

So it does not appear necessary to migrate to .editorconfig for our analyzer configuration.

[iSazonov]

.Net team add new rules in .globalconfig continuously. There may be rules, for example, for recommending new APIs. We won't see them until we update our file. But this won't be necessary if we just use the latest file from the SDK.