fix(angular): use regex-based else-if pattern matching to match Angular's ELSE_IF_PATTERN

[Brooooooklyn]

Angular uses the regex /^else[^\S\r\n]+if/ to detect "else if" connected
blocks, which means block names like "else ifx" also match as chained
else-if branches. Our parser was using exact string matching ("else if"),
causing names like "else ifx" to fall through to the default BlockType::If
and emit two independent conditionals instead of a single chained one.

Fix by reusing is_else_if_pattern() (made public) in the parser's block
type classification, matching Angular's regex-based connected-block detection.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

---

Note

Low Risk
Small, well-scoped change to control-flow block classification with a targeted regression test; low risk outside of slight behavior changes for unusual @else … block names.

Overview
Aligns @else if connected-block detection with Angular by switching from exact string matching ("else if") to regex-equivalent prefix matching via is_else_if_pattern() when classifying block types.

Exports is_else_if_pattern() from control_flow.rs for reuse in the HTML parser and adds a regression test ensuring inputs like @else ifx (...) are still chained as an ElseIf branch (mirroring Angular behavior).

^{Written by Cursor Bugbot for commit 5c4bf54. This will update automatically on new commits. Configure here.}

[Brooooooklyn]

• fix(angular): use regex-based else-if pattern matching to match Angular's ELSE_IF_PATTERN #36 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.