Enable template localization on dotnet CLI

[bekir-ozturk]

Background:

Template engine (dotnet new) added support for template localizations in .NET 6.0. This new system replaces the old way of localizing templates that only worked on Visual Studio and works on both .NET CLI as well as VS.

This PR introduces changes to switch to the new template localization system.

Summary of the changes

• Adds <UsingToolTemplateLocalizer>true</> to projects containing templates.
• Adds necessary id fields into template.json files to allow localizing certain fields (specifically, post actions).
• Generates localization files to be translated by loc team

What to expect after merging

Every time there is a change to one of the templates:

• The dev making the change should build (at the very least) the modified template project. This will update the loc files on the local working copy,
• Push the loc files together with the template modifications. Review & merge.
• OneLocBuild integration will automatically pick up the changes and will send them for translation.
• You will receive a PR containing the translated template loc files when they are ready. Review & merge.

Microsoft Reviewers: Open in CodeFlow

[RussKie]

There appears to be a lot of "noisy" changes, that don't carry any value.

[RussKie]

Why was this changed?

[bekir-ozturk]

In some cases, loc team used hard spaces that won't break into a new line instead of a regular whitespace character. Our automated tool is configured to encode such symbols into \u#### form.
Hopefully, the tooling they are using will be able to deal with this change. But if starts going back and forth, we will update the tool to preserve the current encoding.

[dreddy-work]

@bekir-ozturk , this change is causing the problem. Loc pipeline converted this back to its original state removing the \u####. But local build adds it back and thus every time you sync with main and try to build repo locally, you will be getting this unwanted change as modified one. Is this change communicated to loc pipeline?

[ghost]

Hello @RussKie!

Because this pull request has the :octocat: automerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[ghost]

Happy to oblige