Fix inline highlighter quote handling for Shell and JS/TS nested expressions

[Copilot]

Shell strings containing $() or ${} and JS/TS template literals with nested ${} caused "phase reversal" - content inside and outside quotes was incorrectly swapped. The regex-based tokenizer couldn't handle nested structures.

# Before: tokenized as ["][hello ][$(whoami)][ world]["]
# After:  tokenized as ["hello $(whoami) world"]
echo "hello $(whoami) world"

// Before: tokenized as [`Nested ${`][inner][`}`]
// After:  tokenized as [`Nested ${`inner`}`]
const x = `Nested ${`inner`}`

Changes

• Shell/Bash (bash, sh, zsh, fish):

  • parseShellDoubleQuotedString: Handles $(), ${}, backticks, escapes within double-quoted strings
  • parseShellCommandSubstitution: Handles nested parens and quotes inside $()
  • tokenizeShell: State-based tokenizer replacing regex for strings

• JavaScript/TypeScript (js, ts, jsx, tsx, etc.):

  • parseJsTemplateString: Handles ${} interpolation in template literals
  • parseJsTemplateExpression: Handles nested templates, strings, braces inside ${}
  • tokenizeJsTs: State-based tokenizer for template literals

The tokenize() function now dispatches to language-specific tokenizers based on the language parameter.

Original prompt

inlinedhighlighterの、"や'の扱いが雑。ASTは使いたくないが、もうちょいちゃんとやって。bashとかの、$()や、閉じるとき、"が認識されず、フェーズが移らず、その後、"の中身と外が逆転する。この逆転現象が起きないようになれば、ある程度のミスもまぁいい。できるだけ正確に。

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.