Set CLSCompliant attribute where possible

[WolfgangHG]

We set "CLSCompliant" it to "true" in our projects because our application provides a VB.NET based scripting, and thus all libraries that could be accessed by the VB.NET code should be CLSCompliant (e.g. to avoid the situation "protected member variable and property for this variable with same name, only differing in casing").
After having added the first Kiota generated REST client, I had to disable the "not CLSCompliant" warnings for this client with a ".editorconfig" file.

This pull request tries to make Kiota CLSCompliant.

It is not possible for the project "Microsoft.Kiota.Authentication.Azure" because it has public api using classes from Azure.Core that is also not CLSCompliant. That's why I set the attribute per project.

Only problem:
IParseNode defines a propery of type "sbyte" that is not CLSCompliant:

kiota-dotnet/src/abstractions/serialization/IParseNode.cs

Lines 39 to 43 in 9e4d0e3

	/// <summary>
	/// Gets the sbyte value of the node.
	/// </summary>
	/// <returns>The sbyte value of the node.</returns>
	sbyte? GetSbyteValue();

To my understanding, I can make the projects CLSCompliant anyway, and I just have to disable the warning for all code parts that are not CLS compliant.
This is done by setting [CLSCompliant(false)] where possible. Only the IParseNode interface requires a #pragma warning disable CS3002 because the attribute is not allowed on interface members.

In project "Microsoft.Kiota.Serialization.Json", there was a warning \obj\Debug\netstandard2.1\System.Text.Json.SourceGeneration\System.Text.Json.SourceGeneration.JsonSourceGenerator\MySerialKiotaJsonSerializationContext.SByte.g.cs(19,84,19,89): warning CS3003: Type of 'KiotaJsonSerializationContext.SByte' is not CLS-compliant. that was not suppressible with a ".editconfig" file - it does not accept paths in the "obj" directory.
I first created a roslyn issue (https://www.github.com/dotnet/roslyn/issues/83232), and the bot pointed me to a workaround (https://www.github.com/dotnet/roslyn/issues/47384#issuecomment-3529305512): add a ".globalconfig" file in the project that disables the warning:

dotnet_diagnostic.CS3003.severity = silent

This affects also generated files.

Then add a ".editorconfig" file that enabled the warning again:

[*.{cs}]
dotnet_diagnostic.CS3003.severity = warning

This file does NOT affect generated files, so the warning from them is still suppressed by ".globalconfig".

As there was also a suppression workaorund for "CS1591: Missing XML comment..." in "Microsoft.Kiota.Serialization.Json" that should probably also affect only generated files, I moved this suppression also to the new files.

Roslyn already contains a fix (https://www.github.com/dotnet/roslyn/pull/82224) so that you can specify suppressions for generated paths in ".editorconfig", but this fix does not seem to be released.

Hope my idea is acceptable ;-)

[baywet]

Thanks for the contribution!