Allow share template name for different languages

Is your feature request related to a problem? Please describe.

I writing templates for F* language which provide exporting to F#. I want make consuming F* programs in .NET ecosystem to be as easy as possible. So I create template https://github.com/kant2002/fstarmsbuildsdk and by mistake do not change short template for template, but do change

1. Package identity
2. Language

Currently when I run dotnet new console --lang F* I receive following error message

Unable to resolve the template, the following installed templates are conflicting:
Identity                  Template Name  Short Name  Language  Author         Package

------------------------  -------------  ----------  --------  -------------  --------------------------------------------
FStarLang.Common.Console  Console App    console     F*        Andrii Kur...  FStarLang.DotNet.Common.ProjectTemplates.1.0
Microsoft.Common.Console  Console App    console     C#,F#,VB  Microsoft


Uninstall the template packages containing the templates to keep only one template from the list or add the template options which differentiate the template to run.

Describe the solution you’d like

Would be good that package resolution would take into account switch --lang here and resolve template not only on short name, but on short name + language.

Additional context

Other languages which may benefit from this

• C compiler for .NET https://github.com/fornever/cesium
• Zig probably https://github.com/vezel-dev/zig-sdk
• IronXXX family.
• Pascal.ABC http://pascalabc.net/en/

[baronfel]

@phenning this new template would be for F-Star, a proof language that is distinct from F# 😃

[vlada-shubina]

Moving the issue to dotnet/templating for the planning purposes.

Short time solution - workaround It is already possible to achieve the desired behavior, though a bit odd. The solution is to use the same groupIdentity as Microsoft template: here Microsoft.Common.Console. It makes the template appear in the same line/group in dotnet new. You can check https://www.nuget.org/packages/Peachpie.Templates - they are already doing that. @phenning please let us know if there are any concerns for Visual Studio here.

Medium time solution

• Implement https://github.com/dotnet/templating/issues/4135 so the conflicts can be resolved by user.
• Allow disambiguation via --language (this issue)
• For the languages available from SDK, use SDK templates by default
• Update documentation on group identity: https://github.com/dotnet/templating/issues/2384

Long time solution

• https://github.com/dotnet/templating/issues/5357 - rename group identities so they are associated with DotNet and not Microsoft. This is not an easy task due to backward compatibilities.