fix(linter): pre-compile jest assert-function patterns and skip invalid ones

[shulaoda]

matches_assert_function_name (used by jest/prefer-ending-with-an-expect) recompiled every pattern with Regex::new(...) on every node visited — a hot path — and used .unwrap(), so a user-supplied assertFunctionNames pattern that expands to an invalid regex (e.g. "[" → (?ui)^[(\.|$)) would panic the linter.

Patterns are now compiled once when the rule config is built (mirroring the existing expect-expect rule), stored in a #[serde(skip)] field, and matches_assert_function_name takes the pre-compiled &[Regex]. Invalid patterns are skipped via Regex::new(...).ok() instead of panicking. This fixes both the per-call recompilation and the panic.

Regression tests: a malformed pattern no longer panics and the test block is still reported; a valid pattern alongside a malformed one still matches.

[codspeed-hq]

Merging this PR will not alter performance

✅ 5 untouched benchmarks
⏩ 66 skipped benchmarks¹

---

_{Comparing shulaoda:06-19-fix_jest_assert_function_pattern (75f1fc2) with main (eb8bedc)}

Footnotes

1. 66 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩