Rename legacy s_-prefixed private fields to camelCase and enforce the rule

[ChrisonSimtian]

Problem

.editorconfig:73-85 mandates camelCase private fields (no _/m_/g_/s_
prefix, per CSharpGuidelines AV1702/AV1705) but keeps severity = suggestion
because ~35 legacy s_-prefixed identifiers across ~34 files still violate it
(e.g. Telemetry.s_confirmedVersion). The convention is documented but not
compiler-enforced, so new violations slip in. Surfaced in #451 review.

Outcome

No prefixed private fields remain; the naming rule is warning, so new
violations fail the build.

Acceptance criteria

• All s_/_/m_/g_-prefixed private fields in src/**/*.cs renamed to camelCase
• dotnet_naming_rule.private_fields_should_be_camel_case.severity bumped suggestion → warning (.editorconfig:78)
• Build green with no new naming warnings

Notes

Mechanical rename; exclude generated code. Low priority.

[IT-VBFK]

I think we should not chasing these "violations".. just fix them when we get around

[ChrisonSimtian]

yep i agree but we can log against this issue when we come across something or someone does a targeted sweep 🧹.
It also reflects a certain code style that we want to see established as opposed to what the code base currently looks like 😅

Basically like the postit next to your messy bedroom that says "tidy room tidy mind" to hopefully encourage us to one day clean up 😂

[YousifSala7]

Hi @ChrisonSimtian @ITaluone , I would like to take this issue. could you please assign it to me?

[ITaluone]

Sure.. thanks for helping out