Use markdownDescription for a few more settings

[mjbvz]

Let's us use inline code elements on these

[Copilot]

Pull request overview

Updates a handful of built-in extension settings metadata to use markdownDescription so their descriptions can render inline code formatting (and adjusts corresponding localized strings accordingly).

Changes:

• Switch select configuration entries from description to markdownDescription in extension package.json manifests.
• Update localized description strings to use Markdown inline-code (backticks) where appropriate.

Reviewed changes

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

Show a summary per file

File	Description
extensions/typescript-language-features/package.nls.json	Updates the node path setting description text to use inline-code formatting.
extensions/typescript-language-features/package.json	Switches the TS Server node path setting descriptions to markdownDescription.
extensions/npm/package.nls.json	Updates a couple of npm setting descriptions to use inline-code formatting.
extensions/npm/package.json	Switches two npm settings to markdownDescription to render inline-code properly.
extensions/json-language-features/package.nls.json	Updates JSON schema-related descriptions to use inline-code formatting for patterns and wildcards.
extensions/json-language-features/package.json	Switches several JSON schema configuration property descriptions to markdownDescription.
extensions/emmet/package.nls.json	Updates Emmet vendor-prefix descriptions to use inline-code formatting.
extensions/css-language-features/package.nls.json	Tweaks selector-separator descriptions to use inline-code formatting.
extensions/css-language-features/package.json	Switches valid-properties lint settings to markdownDescription.

---

You can also share your feedback on Copilot code review. Take the survey.