chore: replace Biome with oxlint, oxfmt and Knip

[Thomasims]

Moves this repository off Biome and onto the shared
@antelopejs/tooling-configs
presets, in step with the rest of the ecosystem.

Tooling swap

• @biomejs/biome and biome.json are gone.
• oxlint (pinned to 1.81.0, the version the presets' JS plugin API matches),
  oxfmt, knip, oxlint-tsgolint and eslint-plugin-perfectionist come in as
  dev dependencies.
• New oxlint.config.ts, oxfmt.config.ts and knip.config.ts, each extending
  the shared preset.
• Scripts: lint → oxlint, lint:fix → oxlint --fix, format → oxfmt .,
  plus new format:check and knip. Every other script is untouched. CI gains
  pnpm format:check and pnpm knip next to the existing pnpm lint, in its
  own ci: commit.

The .github/ISSUE_TEMPLATE/** ignore in oxfmt.config.ts is temporary: those
files are Markdown templates with a .yml extension, which oxfmt cannot parse.
It goes away once
tooling-configs#5 ships
the shared ignore.

tsconfig

Type-aware linting runs through tsgolint, which rejects compiler options
TypeScript 7 removed and auto-discovers each file's tsconfig.json. The only
offender here was "moduleResolution": "node" (the removed node10), so the
field is dropped; tsgolint only objects to the explicit value, and the default
for module: "commonjs" is the same resolver, so the emit is unaffected.

"module": "commonjs" deliberately stays. Raising it to node16 looks like the
obvious fix and is a runtime break: tsc would stop downlevelling dynamic imports
and emit native ESM ones, bypassing the CommonJS resolver detour the ajs
runtime installs.

What the linter forced

Import order, and nothing else. perfectionist(sort-imports) autofixed every
error; import(no-cycle) found no cycles in this tree. Nothing was disabled and
no rule was silenced. The remaining oxlint output is warnings only
(no-redundant-type-constituents on the decorator overload unions,
unbound-method, no-base-to-string) — the deliberate backlog the presets ship
with, left alone here.

Knip

One real finding: src/logging/index.ts exports the Logging namespace both
named and as the default, which Knip reports as a duplicate export. Both
spellings are used by consumers across the ecosystem (import { Logging } from "@antelopejs/interface-core/logging" and import Logging from … both appear in
shipped modules), so this is published contract, not an oversight. Knip's tags
filter does not reach the duplicate-export check, so the issue is silenced by
path in knip.config.ts with
ignoreIssues: { "src/logging/index.ts": ["duplicates"] }; the duplicate-export
check stays on for the rest of the repository, and the reason is recorded
inline.

No exports were removed. This package is a versioned contract: its surface is
reachable only from consumers Knip cannot see, so an "unused export" here would
never be evidence of dead code.

Verification

• Public surface unchanged. dist was built from untouched origin/main
  and from this branch, and the runtime export keys of every module reachable
  through the exports map (., ./config, ./logging, ./logging/* and the
  ./* wildcard — 11 modules in all) were diffed: identical. The .d.ts file
  set is identical too, and the only .d.ts byte difference is a reordered
  import line in modules.d.ts. The compiled .js differences are likewise
  reordered require calls and nothing else.
• Build succeeds with no source changes beyond the import sort.
• Tests. pnpm test on untouched origin/main: 75 passing, 0 failing. On
  this branch: 75 passing, 0 failing. pnpm test:package fails identically on
  both — it shells out to corepack, which is not on this machine — so it is
  environmental and pre-existing, not a regression from this change.
• pnpm lint, pnpm knip and pnpm build all exit 0.

Commits

The oxfmt pass is its own commit and is recorded in .git-blame-ignore-revs, so
git blame stays readable. oxfmt also normalizes package.json key order and
sorts keywords; that is expected.