Fix/Remove LEAN warnings

[Marinovsky]

Description

Removed the following warnings:

• IDE0066: Use switch expression (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/ide0066)
• CA1062: All reference arguments that are passed to externally visible methods should be checked against null (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1062)
• CA1707: Identifiers should not contain underscores (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1707)
• CA1002: Do not expose generic lists (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1002)
• CA1051: Do not declare visible instance fields (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1051)
• CA1819: Properties should not return arrays (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1819)
• CA1725: Parameter names should match base declaration (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1725)
• CA2211: Non-constant fields should not be visible (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2211)

Fixed these warnings:

• CA2000 (Just in unit tests): Dispose objects before losing scope (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2000)
• CA2201 (Created new class called TestException): Do not raise reserved exception types (see https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2201)
• CS1591 (There are still like 300 hundred missing): Missing XML comment for publicly visible type or member (see https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs1591)

Related Issue

Closes #5155

Motivation and Context

With this change we will ignore the warnings that are acceptable in our codebase to reduce build logs and improve visibility into new warnings and errors

Requires Documentation Change

N/A

How Has This Been Tested?

N/A

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

[Martin-Molinero]

This PR is too big to review & ship, it will be resubmitted 1 PR at the time with a reasonable amount of changes as requested, ~100 fixes per PR 🙏