Fix CA1000/S4023/S3442/S107/SA1402/SA1649 warnings

[iamdmitrij]

Pull Request

The issue or feature being addressed

#1290

• Enable CA1000 check only for non-public types
• Make S4023 a suggestion
• Fix S3442 by making abstract classes constructors private
• Set S107 max param count to 12
• Disable SA1402 because this repo doesn't follow such file/class structure
• Fix SA1649 by consolidating class/file names. As far as I can tell it doesn't break any public APIs, just renaming C# source files
• Add eng/analyzers configs to solution file in Solution Items

Details on the issue fix or feature implementation

Confirm the following

• I started this PR by branching from the head of the default branch
• I have targeted the PR to merge into the default branch
• I have included unit tests for the issue/feature
• I have successfully run a local build

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.72%. Comparing base (3c642fd) to head (a6acc1a).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2089   +/-   ##
=======================================
  Coverage   83.72%   83.72%           
=======================================
  Files         312      312           
  Lines        7126     7126           
  Branches     1054     1054           
=======================================
  Hits         5966     5966           
  Misses        789      789           
  Partials      371      371           

Flag	Coverage Δ
linux	83.72% <100.00%> (?)
macos	83.72% <100.00%> (?)
windows	83.72% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[martincostello]

Your PR has conflicts that need resolving.

Before starting a PR, ensure your fork is up to date and create a branch (don't work off main).

[iamdmitrij]

@martincostello could you clarify what conflicts are we talking about? Merge conflicts? If so I don't see them on this PR

And my fork is up to the date

[martincostello]

Ah, it's because the merge method was set to rebase:

The recommendation still stands though - if you do any further PRs, please sync your fork with our main branch and then create a new branch before starting new work.