Add Chinese descriptions and examples to config files

[frankslin]

• Add description_zh field with Traditional Chinese descriptions to all 14 config files
• Add examples field with typical conversion examples for each config
• Add config-examples.test.js to validate conversion examples
• Examples demonstrate differences between variants (e.g., s2tw vs s2twp)

Example conversions:

• s2t: "鼠标" → "鼠標" (standard Traditional)
• s2tw: "鼠标" → "滑鼠" (Taiwan standard)
• s2twp: "数据库" → "資料庫" (Taiwan with phrases)

Also: clarify Traditional Chinese as OpenCC Standard in 2t and t2 configs

Update all 2t and t2 config files, except jp2t and t2jp, to specify 'OpenCC標準繁體' (OpenCC Standard Traditional Chinese) instead of just '繁體' (Traditional Chinese). This clarifies that it represents an intermediate standard format, not a final user-facing variant.

Modified configs:

• s2t.json: 簡體到繁體 → 簡體到OpenCC標準繁體
• t2s.json: 繁體到簡體 → OpenCC標準繁體到簡體
• hk2t.json: 香港繁體到繁體 → 香港繁體到OpenCC標準繁體
• t2hk.json: 繁體到香港繁體 → OpenCC標準繁體到香港繁體
• t2tw.json: 繁體到台灣正體 → OpenCC標準繁體到台灣正體
• tw2t.json: 台灣正體到繁體 → 台灣正體到OpenCC標準繁體

Note: The 't' in jp2t/t2jp refers to Japanese Kyūjitai (舊字體), not Chinese OpenCC Standard Traditional, so these should not be labeled as 'OpenCC標準繁體'.

[Copilot]

Pull request overview

This PR enhances the OpenCC configuration files by adding Traditional Chinese descriptions and conversion examples to all 14 config files. It also clarifies terminology by specifying "OpenCC Standard Traditional Chinese" for intermediate 2t and t2 conversions (except Japanese variants).

Key Changes

• Adds description_zh field with Traditional Chinese descriptions to all config files
• Adds examples field with input/output conversion examples demonstrating variant differences
• Adds test file config-examples.test.js to validate conversion examples
• Updates config names to clarify "OpenCC Standard Traditional Chinese" terminology

Reviewed changes

Copilot reviewed 18 out of 35 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
wasm-lib/test/config-examples.test.js	New test file to validate conversion examples from config files
wasm-lib/test/check-conversions.js	Helper script for manually checking conversions (development tool)
wasm-lib/scripts/find-variant-examples.js	Helper script for finding character variants (development tool)
wasm-lib/package.json	Updates test script to include new config-examples test
wasm-lib/data/config/*.json (14 files)	Adds description_zh and examples fields to all config files
wasm-lib/dist/data/config/*.json (14 files)	Mirrored changes to dist config files
wasm-lib/dist/esm/index.js	Updates module path resolution logic
wasm-lib/dist/esm/opencc-wasm.js	Minified WASM glue code with updated file reference
wasm-lib/dist/cjs/index.cjs	Updates CommonJS module path resolution

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The converter is being cached and reused across multiple async tests. Since OpenCC.Converter() returns a promise (as indicated by await convert(example.input) on line 37), there's a potential race condition where the converter might not be properly initialized before being used in a test.

The cache should store the result of awaiting the converter promise, not the promise itself. Consider changing line 18 to:
converterCache.set(config, await OpenCC.Converter({ config }));

And make the function async:
async function getConverter(config) { ... }

[Copilot]

The test is created at the top level (outside of a describe block) by iterating over config files synchronously, but the test callback is async. The getConverter() call should be awaited since it needs to be async to properly await the converter initialization.

Change line 36 to:
const convert = await getConverter(configFile);