Ignore warnings in MVVM generated sources

Until we generate sources based on regulated and acceptable set of code-style rules,
warnings for the MVVM generated sources should be ignored for a clean build.

We know and acknowledge these warnings and they shouldn't bloat our build logs.

Author: Nirmal4G

UnitTests/UnitTests.Shared/.editorconfig

@@ -1,7 +1,35 @@
-[*.{cs,vb}]
 
-# SA1601: Partial elements should be documented
+# Analyzer Configurations for Unit Test sources
+
+# C# Source Files
+[*.cs]
+
+# A C# partial element is missing a documentation header.
 dotnet_diagnostic.SA1601.severity = none
+
+# The Parameter has no matching param tag in the XML comment.
 dotnet_diagnostic.CS1573.severity = none
+
+# Missing XML comment for publicly visible type or member.
 dotnet_diagnostic.CS1591.severity = none
-dotnet_diagnostic.CS1712.severity = none
+
+# The Type parameter has no matching typeparam tag in the XML comment.
+dotnet_diagnostic.CS1712.severity = none
+
+
+# Analyzer Configurations for MVVM Source Generated test sources
+
+# C# Source Files
+[Microsoft.Toolkit.Mvvm.SourceGenerators/**.cs]
+
+# Prefix local calls with this
+dotnet_diagnostic.SA1101.severity = none
+
+# The file header XML is invalid.
+dotnet_diagnostic.SA1633.severity = none
+
+# File name should match first type name.
+dotnet_diagnostic.SA1649.severity = none
+
+# Non-nullable field 'value' must contain a non-null value when exiting constructor.
+dotnet_diagnostic.CS8618.severity = none