Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

* fix: track angle brackets in value expressions

* chore: add tests

* chore: apply automated updates

* fix: include digits in generic identifier check and add edge-case tests

Use `\w$` instead of `[A-Za-z_$]` so identifiers ending in digits
(e.g. `Map2<T>`) are recognized as generics. Add tests for nested
generics and digit-ending identifiers.

* fix(analyze): distinguish generics from comparisons with digit-only operands

`\w` and `[A-Za-z0-9_$]` both match bare digits, so `1<2` was
incorrectly treated as a generic. Walk back to the start of the word
and verify it begins with a letter/underscore/$ (valid JS identifier).

* fix(analyze): skip `>` in arrow tokens `=>` when tracking angle brackets

The `>` in `=>` inside generic type annotations was decrementing
angleDepth, causing commas after the arrow to be treated as declaration
separators (e.g. `Map<(x: string) => void, string>`).

* chore: apply automated updates

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Pooya Parsa <pooya@pi0.io>