fix(anti-slop): honor disable-next-line before asserted expression

[howmanysmall]

Summary

 hasSafetyComment
   safety marker before ancestors
-  if tsgolint reports on assertion syntax
-    accept a disable that covers the assertion line
+  accept disable-next-line on the line before `as`
+    even when the comment sits inside the asserted expression
+  if tsgolint reports on assertion syntax
+    also accept same-line and block disables that cover `as`
   else
-    accept a disable before the enclosing statement
+    also accept a disable before the enclosing statement

type({ ... }).readonly() as unknown as Type<BunFile> with the suppression on the line before as is a justification. The old path only saw that comment when it already knew oxlint-tsgolint was 7.0.2002 or newer.

Evidence

• Before: the rule reported missingSafetyComment on both as unknown and as Type<BunFile> even with // oxlint-disable-next-line typescript/no-unsafe-type-assertion -- slopware immediately above the assertion.
  After: nr test:agent -- tests/rules/anti-slop/require-safety-comment-for-type-assertion.test.ts passes, including that case with no tsgolintVersion setting.

Merge Danger

Door: two-way

Revert the rule and the test. No data migration.

Blast Radius: consumers

Fewer require-safety-comment-for-type-assertion reports when a described disable-next-line sits on the line before as. Same-line disable-line still depends on the 7.0.2002 diagnostic range.

[github-actions]

Bundle size

Artifact	Base	Pull request	Change
dist/index.js	484.18 kB	484.21 kB	+25 B (+0.01%)

_{Raw, uncompressed bytes from the minified prepublishOnly build. Measured for commit d873c26 against base 21291c7.}