fix(pipeline): respect quotes when parsing template expressions

[Agnik47]

Summary

Pipeline template expressions (${{ ... }}) are parsed without regard to quotes, so two ordinary shapes render wrongly. There is no tracking issue; the repro is below.

Expression	Before	After
${{ 'https://x.test/' + item.id + '/' }}	https://x.test/' + item.id + '/ (its own source text)	https://x.test/7/
${{ 'x' === 'x' ? 'yes' : 'no' }}	source text	yes
${{ item.tags | join(' | ') }}	the unjoined array, filter silently skipped	a | b | c
${{ 'a|b' }}	undefined	a|b

Two causes in src/pipeline/template.ts:

• The quoted-literal fast path matched anything that starts and ends with the same quote (/^(['"])(.*)\1$/), so a concatenation or ternary wrapped in string literals was returned as text instead of being evaluated.
• Filters were split on every single |, including one inside a quoted string.

Changes

• The fast path now only accepts a literal whose body contains neither its delimiter nor a backslash. Everything else falls through to the existing path lookup and VM evaluation, which also means escapes such as 'it\'s' are now evaluated properly.
• Filter segments are split by a small quote-aware scanner. If a quote is unterminated (for example default(it's)), the quotes are not string delimiters, so it falls back to the previous split and behaviour is unchanged.

Type of Change

• 🐛 Bug fix

Verification

• 7 new tests in src/pipeline/template.test.ts; 5 fail on main, the other 2 pin behaviour that already worked
• npx vitest run --project unit src/pipeline (108 pass)
• npm run typecheck

[github-actions]

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

• Some automated findings could not be verified against the pull request diff.

This review is advisory and does not block merging.