feat: support dynamic template for vsc

[tecton]

Feature: https://msazure.visualstudio.com/Microsoft%20Teams%20Extensibility/_queries/query/f1a663ad-a677-451b-b990-2f653b78b972/

Impact:

• CLI use template name instead of virtual capability name when scaffolding.
• Template data are moved from fx-core to templates folder.

This pull request introduces significant improvements to the TeamsFx CLI template system, focusing on modernizing how templates are listed, selected, and displayed in the CLI, as well as enhancing localization and resource management. The changes streamline template handling, improve user experience when creating new projects, and clean up outdated or redundant localization strings.

Key changes:

Template Listing and Selection

• Refactored the CLI template listing and selection logic to use a new listAllTemplates function, which retrieves templates based on the platform and groups them by name, replacing the previous capability-based approach. This simplifies template management and ensures consistency across platforms. [1] [2]
• Updated the CLI create command to use template names directly for selection, preset programming language when not specified, and improved command examples for clarity and relevance. [1] [2]

Output Formatting and Display

• Improved the formatting of the template list output in the CLI by updating the table rendering logic to better handle template names and descriptions, making the output more readable and user-friendly. [1] [2]

Localization and Resource Management

• Enhanced the localization utility to support loading translation files from both the fx-core and template resource folders, including support for cached resources, ensuring that localized strings are always up to date and correctly merged.
• Cleaned up the localization resource file by removing obsolete or unused capability and project type strings, reducing clutter and potential confusion. [1] [2] [3]

Build and Release Process

• Updated the GitHub Actions release workflow to include additional artifacts (fallback and metadata.zip) when creating template releases, ensuring all necessary files are published.
• Switched the clean script in fx-core to use rimraf for better cross-platform compatibility.
• Updated .gitignore to exclude new resource and build artifacts, keeping the repository clean.