Update project templates use primary constructors and collection expressions

[Varorbc]

update project templates use primary constructors

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Description

Fixes #52893

[Varorbc]

@danroth27 ping

[danmoseley]

@Varorbc apologies for delay.
@captainsafia I believe you own area-mvc which includes most templates? could you have a look?

[captainsafia]

Thanks for this contribution!

It looks great overall! The move to primary constructors here has revealed places where we were initializing but not using ILoggers. I think it might be worthwhile to continue to inject ILogger's into the classes via the primary constructor but add code to use them in the class so that the functionality is properly demonstrated.

[Varorbc]

@captainsafia ping

[guardrex]

@captainsafia ... I think we'll have two documentation example changes to mirror these updates. I'll take care of opening and working the doc issue.

[captainsafia]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[captainsafia]

LGTM!

Our existing template tests give us good coverage here and we'll be able to do some manual validation on this change once it flows through to main.