Address review comment from sonar-review-alpha on packages/jsts/src/rules/S125/rule.ts

Comment: The `/i` flag is too broad for `NOTE` (and to a lesser extent `HACK`). Both are common English prose words. A comment block like:

```
// Note that we disabled this temporarily.
// const x = processVector(name, type);
```

will match `\bNote\b` (case-insensitive), `containsCode` returns false for the first line, so `hasTaskMarker` returns `true` and the genuine commented-out code is silently suppressed.

`TODO`, `FIXME`, and `XXX` are almost never used as natural English prose in comments, so `/i` is low-risk for those. `NOTE` is different — it appears constantly in developer prose (`// Note that...`, `// Note:`, `// NOTE:` are all equivalent under `/i`).

Remove the `/i` flag and match uppercase only, which is the de-facto convention for all five task markers. The `@TODO` test case still passes because `\b` matches before the `T` in `@TODO`. If lowercase support is truly needed, enumerate the exact mixed-case forms you want rather than accepting all cases.

- [ ] Mark as noise

Author: Vibe Bot

packages/jsts/src/rules/S125/rule.ts

@@ -28,7 +28,7 @@ import path from 'node:path';
 
 const EXCLUDED_STATEMENTS = new Set(['BreakStatement', 'LabeledStatement', 'ContinueStatement']);
 
-const TASK_MARKER_PATTERN = /\b(TODO|FIXME|HACK|XXX|NOTE)\b/i;
+const TASK_MARKER_PATTERN = /\b(TODO|FIXME|HACK|XXX|NOTE)\b/;
 
 // Cheap prefilter: any meaningful JS statement must contain at least one of these characters,
 // or be an import/export with a string literal (side-effect imports have no punctuation)