refactor(content-mapper-vitepress): restore the @VUE scope

`@vue/content-mapper-vitepress` shares the `@vue/content-mapper` prefix, so
the package family reads as one thing; the directory and the VS Code bundle
names follow the published name.

Author: johnsoncodehk

extensions/vscode/rolldown.config.ts

@@ -11,8 +11,8 @@ export default defineConfig({
 		'typescript-plugin': './node_modules/@vue/typescript-plugin/index.ts',
 		'content-mapper-server': '../../packages/content-mapper/server.ts',
 		'content-mapper-worker': '../../packages/content-mapper/worker.ts',
-		'vitepress-content-mapper-server': '../../packages/vitepress-content-mapper/server.ts',
-		'vitepress-content-mapper-worker': '../../packages/vitepress-content-mapper/worker.ts',
+		'content-mapper-vitepress-server': '../../packages/content-mapper-vitepress/server.ts',
+		'content-mapper-vitepress-worker': '../../packages/content-mapper-vitepress/worker.ts',
 	},
 	output: {
 		format: 'cjs',

extensions/vscode/schemas/vue-content-mapper-tsconfig.schema.json

@@ -11,7 +11,7 @@
 						"package": {
 							"enum": [
 								"@vue/content-mapper",
-								"vitepress-content-mapper"
+								"@vue/content-mapper-vitepress"
 							]
 						}
 					}

extensions/vscode/src/extension.ts

@@ -320,9 +320,9 @@ function registerTypeScriptContentMapper(context: vscode.ExtensionContext) {
 				),
 				createContribution(
 					['.md'],
-					'vitepress-content-mapper',
-					'vitepress-content-mapper-server.js',
-					'vitepress-content-mapper-worker.js',
+					'@vue/content-mapper-vitepress',
+					'content-mapper-vitepress-server.js',
+					'content-mapper-vitepress-worker.js',
 				),
 			],
 		));

…kages/vitepress-content-mapper/README.md …kages/content-mapper-vitepress/README.mdpackages/vitepress-content-mapper/README.md renamed to packages/content-mapper-vitepress/README.md packages/vitepress-content-mapper/README.md renamed to packages/content-mapper-vitepress/README.md

@@ -1,6 +1,6 @@
 # VitePress content mapper
 
-`vitepress-content-mapper` type-checks VitePress markdown with `tsc` through the TypeScript
+`@vue/content-mapper-vitepress` type-checks VitePress markdown with `tsc` through the TypeScript
 content-mapper protocol. It turns a markdown file into the SFC shape that VitePress renders —
 frontmatter, fenced code blocks and `<<<` snippet imports blanked, `<script>` / `<style>` blocks
 lifted out, the remaining markdown as the template — and reuses `@vue/content-mapper`'s project
@@ -14,7 +14,7 @@ Install it beside the Vue mapper, then register both in `tsconfig.json`:
 {
 	"contentMappers": [
 		{ "package": "@vue/content-mapper", "extensions": [".vue"] },
-		{ "package": "vitepress-content-mapper", "extensions": [".md"] }
+		{ "package": "@vue/content-mapper-vitepress", "extensions": [".md"] }
 	]
 }
 ```

…es/vitepress-content-mapper/package.json …es/content-mapper-vitepress/package.jsonpackages/vitepress-content-mapper/package.json renamed to packages/content-mapper-vitepress/package.json packages/vitepress-content-mapper/package.json renamed to packages/content-mapper-vitepress/package.json

@@ -1,5 +1,5 @@
 {
-	"name": "vitepress-content-mapper",
+	"name": "@vue/content-mapper-vitepress",
 	"version": "3.3.11",
 	"license": "MIT",
 	"files": [
@@ -11,7 +11,7 @@
 	"repository": {
 		"type": "git",
 		"url": "https://github.com/vuejs/language-tools.git",
-		"directory": "packages/vitepress-content-mapper"
+		"directory": "packages/content-mapper-vitepress"
 	},
 	"typescript": {
 		"contentMapper": {