Fix offending l10n.t call and add an eslint rule to prevent it from happening

[TylerLeonhardt]

ref #277576

[Copilot]

Pull Request Overview

This PR fixes an incorrect usage of vscode.l10n.t() that used template literal string interpolation and adds an ESLint rule to prevent similar issues in the future. The localization API requires placeholder-based formatting (e.g., {0}) rather than template literals.

Key Changes:

• Fixed the offending vscode.l10n.t() call to use proper placeholder syntax instead of template literal interpolation
• Added a new ESLint rule to detect and prevent template literals in localization function calls
• Enabled the new rule in the ESLint configuration as an error

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
extensions/typescript-language-features/src/languageFeatures/quickFix.ts	Changed template literal interpolation to use placeholder {0} syntax in vscode.l10n.t() call
eslint.config.js	Enabled the new code-no-localization-template-literals rule as an error
.eslint-plugin-local/code-no-localization-template-literals.ts	Implemented new ESLint rule that detects template literals in vscode.l10n.t() and nls.localize() calls