Consider moving to _privateField to follow the official C# style guide and reduce naming collisions

Question and/or Comment

Hey there recently when playing around a bit in the stride source code I noticed that Stride currently uses camelCase for private fields.
This makes it very annoying to work with parameters with the same name.

To work around this issue often parameters are suffixed or strangly named values (see CommandList as an example)
I would like to ask if it is possible to loose this restriction or move to the standard style guide of C# and use _privateField instead.
As far as I can see it there wouldn't be compatibility issues as I only suggest naming changes for private fields.

See here for reference https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/identifier-names

The issue points to Stride's source code and CommandList as an example; begin by reviewing that example and the linked official C# identifier-naming guide. Determine the project-wide scope of private-field renames and whether the proposed convention is agreed on. Done means the agreed private-field naming change is applied consistently without compatibility issues.