More lint/format actions

[musjj]

I feel that the project can use a bit more CI actions around linting and formatting.

For linting we could simply run dotnet build while treating warnings as errors:

$ dotnet build -warnaserror

The command will fail if there are any errors or warnings.

For formatting, how about adopting CSharpier? The problem with the native dotnet format is that they don't even support line breaking, IMO one the most valuable benefits to using autoformatters:

• Feature request: Allow me to specify a desired max-column that code should be wrapped against. dotnet/roslyn#15406

The issue is almost 10 years old now and it's unlikely to be fixed any time soon.

To check the formatting with CSharpier, the CI can run:

$ csharpier check .

What do you think?

[jolexxa]

That's a great point. I think now that Chickensoft has recently adopted braces on separate lines (as is typical with C# code), it makes more sense for us to adopt CSharpier now. Definitely on board for this. We would need to make sure we ship VSCode auto-formatting settings out of the box for CSharpier, and likely want to support Rider and Zed as well, too. We'd also want to update the setup guide on the Chickensoft website to instruct users to install CSharpier as a dotnet tool if needed, too.