chore(rescript): remove the 4 orphan .res files + the affine-res package

Removes the ReScript baseline rot that's been failing the
governance / Language / package anti-pattern policy check on every PR:

- packages/affine-res/{README.adoc,rescript.json,src/AffineScript.res,
  AffineScript.resi,AffineScriptValue.res} — orphan ReScript bindings
  package. The whole directory goes because the .res sources are the
  only thing it contains; the README + rescript.json + .resi cannot
  function without them.  Same precedent as packages/affine-ts/
  (removed 2026-05-11, issue #66 closed won't-do): non-AffineScript
  consumer-binding packages aren't first-class in the AffineScript
  repo — TS callers were told to use @hyperpolymath/affine-js
  directly, ReScript callers should do likewise.
- affinescriptiser/examples/SafeDOMExample.res and
  examples/SafeDOMExample.res — duplicate ReScript example.  No
  ReScript-equivalent in the AffineScript stdlib examples bench was
  rebuilt; the equivalent live .affine examples (e.g.
  examples/effects.affine, ownership.affine) cover the same ground.

No other tracked code references `affine-res`, `AffineRes`, or these
example paths (verified via repo-wide grep across .yml/.adoc/.json/
.toml/.affine/.ml/.mli/.rs/.sh/Justfile).  The historical roadmap
status doc docs/reports/AFFINESCRIPT-ROADMAP-STATUS-2026-04-13.md
mentions affine-res as a 2026-04-13 snapshot checkbox; left intact as
history.

Effect: `find . -name '*.res' | grep -v node_modules` returns empty,
which is exactly what the governance script asserts.  No regressions
in the build (these files were never linked into dune / Cargo / the
CLI).

Refs the cross-PR triage on #291, #292 where the same failing check
was diagnosed as baseline rot.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath