Developers enjoy `dotnet format` UXs, in line with VS UXs

# Background
After the template is generated by `dotnet new`, it might not match formatting defined in `.editorconfig` in the output location.
Visual Studio applies `.editorconfig` rules to generated files, making behavior different
**Audience**: users

# Technical details
## Raw thoughts
- optionally run `dotnet format` after `dotnet new` to format the content
- brings `dotnet new` closer to Visual Studio behavior
- respect global and local (repo) editorconfig
- this allows to set the preference on language features as: top-level statements, namespaces etc
- performance might be an issue
- consider sharing the result of MSBuild evaluation to dotnet format if performed
- may remove the need of supporting `--langVersion` parameter in SDK templates (?)
- considering the feature behind feature flag (env var, option?)

# Justification
- UX improvement: Avoids manual step of running `dotnet format` after the template is run
- UX homogeneity: feature parity to Visual Studio UX
- Aligns to .NET modernization OKRs