Enable more code style rules

[RoosterDragon]

Enforces 21 19 style rules across the project, and 2 complier warnings related to XML docs.

I have batched together a PR for these rules as they each had limited existing violations (4 files or less) to resolve. However fixes are arranged per commit so we can easily bikeshed over rules as desired.

See https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/ for explanation of each rule.

[pchote]

These mostly look like good cleanups, except IMO 16 and 37 which i'm not convinced are improvements.

[PunkPun]

I'm concerned about IDE0016. As far as I understand those checks are there to throw early.

Also do add punctuation to the descriptions

[RoosterDragon]

Removals in IDE0016 is my fault. Given our thorough lack of argument null checks in the solution, having just three of them seemed arbitrary so I chose to remove them rather than change. However we could keep those if desired and change to throw expressions, or disable the rule.

[PunkPun]

It might be worth going through git blame and investigatie each situation

[RoosterDragon]

Removed 16 and 37, added missing full stops.

[penev92]

FWIW 37 is somehting we do elsewhere a bunch and IMO it does make sense as a rule.

[penev92]

Suggested change

	# Use explicitly provided tuple name.
	# Prefer explicitly provided tuple element name.

[RoosterDragon]

I've been copy pasting the titles of the docs, e.g. https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/ide0033. Don't feel like changing the approach much for one item.

[penev92]

Weird. I commented because that's not the title VSCode gave me 🤷‍♂️ Alright then, never mind.

[penev92]

Thanks! 🎊

[penev92]

Changelog