Merge branch 'main' into 1.0.0

# Conflicts:
#	.github/workflows/publish_nuget.yml
#	Src/CSharpier.Cli.Tests/CliTests.cs
#	Src/CSharpier.Cli/Options/OptionsProvider.cs
#	docs/CLI.md

Update doc now that I actually may understand how local vs global too…

…ls are invoked

Undo the change to tool command (#1461)

If a tool has a command of `csharpier` then to invoke it as a local tool
you need to use `dotnet csharpier`. Only a globally installed tool works
with `csharpier`. It doesn't seem worth the trouble to change the
command because of that.

If dotnet/sdk#14626 is done, this can be
revisited.

closes #1450

Updating doc for the 1.0.0 release (#1424)

Also realized some options needed to be moved around and supported,
which lead to updating CommandLine after I ran into issues with the
options.

Merge branch 'main' into 1.0.0

# Conflicts:
#	.config/dotnet-tools.json
#	CHANGELOG.md
#	Nuget/Build.props
#	Src/CSharpier.MsBuild/build/CSharpier.MsBuild.targets
#	Src/CSharpier.Tests/CSharpier.Tests.csproj
#	Src/CSharpier.VSCode/CHANGELOG.md
#	Src/CSharpier.VSCode/package.json
#	Src/CSharpier.VSCode/src/DiagnosticsService.ts
#	Src/CSharpier.VisualStudio/CSharpier.VisualStudio/CSharpier.VisualStudio.csproj
#	Src/CSharpier.VisualStudio/CSharpier.VisualStudio/source.extension.vsixmanifest
#	Src/CSharpier.VisualStudio/CSharpier.VisualStudio2019/CSharpier.VisualStudio2019.csproj
#	Src/CSharpier.VisualStudio/CSharpier.VisualStudio2019/source.extension.vsixmanifest
#	Src/CSharpier.VisualStudio/ChangeLog.md
#	Src/CSharpier/SyntaxPrinter/SyntaxNodePrinters/CompilationUnit.cs