chore(deps): update antelope dependencies to latest

[Upd4ting]

Summary

Update every @antelopejs/* reference to the latest published version and pin the antelope core in the repo so pnpm test resolves ajs from node_modules/.bin instead of a global install.

Package	Where	Before (range / resolved)	After (range / resolved)
@antelopejs/interface-core	devDependencies, peerDependencies	>=0.0.3 <1.0.0 / 0.0.3	>=0.1.1 <1.0.0 / 0.1.1
@antelopejs/tooling-configs	devDependencies	^0.0.4 / 0.0.4	^0.0.6 / 0.0.6
@antelopejs/core	devDependencies	not listed (global ajs 1.9.0)	^1.9.1 / 1.9.1
@antelopejs/api	src/antelope.test.ts module source	1.2.4	1.3.0

Fixes required by the upgrade:

• @antelopejs/api 1.3.0 requires a publicBaseUrl config key outside dev mode (MissingPublicBaseUrlError), so the test project now sets publicBaseUrl: "http://127.0.0.1:5010", matching the configured server.
• Removed the ignoreBinaries: ["ajs"] entry and its comment from knip.config.ts, since ajs is now provided by the @antelopejs/core devDependency. The remaining ajs knip hint comes from the tooling-configs preset defaults, not from this repo.

Known, separately tracked issue: the shipped route-lifecycle test ("returns complete registered handlers without replacing the provider") fails when run from the api implementation repo under the current core, because the core resolver wraps objects crossing the interface boundary in facades, so strictEqual on callback/parameters/properties fails. This PR does not touch that test; it passes when run from this repo.

Related issue

None: part of an organization-wide audit keeping antelope dependencies on their latest versions.

Verification

• pnpm install --frozen-lockfile
• pnpm prepack (build)
• pnpm lint (0 errors)
• pnpm format:check
• pnpm knip
• pnpm test with ajs 1.9.1 from node_modules/.bin: 83 passing, 0 failing (loads @antelopejs/api 1.3.0)

Checklist

• The pull request title follows Conventional Commits.
• I added or updated tests when behavior changed. (N/A: no behavior change; only the test project config was adjusted)
• I updated documentation when users or contributors are affected. (N/A: no user-facing change)
• I documented breaking changes and migration steps. (N/A: no breaking change)
• I did not include credentials or unrelated changes.