chore: migrate from eslint to oxlint

[B4nan]

Summary

Replaces ESLint with oxlint, pulling in the shared @apify/oxlint-config preset and oxlint-tsgolint for type-aware rules. Mirrors the migration already shipped in apify-storage-local-js, apify-shared-js, apify-core, apify-client-js, and apify-sdk-js. Prettier remains in place — the oxfmt swap is the next PR.

What changed

• Drop eslint, typescript-eslint, eslint-config-prettier, @apify/eslint-config
• Add oxlint@1.62.0, oxlint-tsgolint@0.22.0, @apify/oxlint-config@^0.2.5
• Replace eslint.config.mjs with oxlint.config.ts; drop unused tsconfig.eslint.json / tsconfig.eslint.website.json
• lint / lint:fix and lint-staged now run oxlint --type-aware
• Drop deprecated baseUrl from tsconfigs and switch the inline paths entries to relative form so oxlint-tsgolint can parse them
• Add noEmit: true to test/tsconfig.json so tsgolint doesn't try to overwrite the e2e .mjs fixtures
• Switch two .ts extension imports in scraper-tools to .js for consistency with the rest of the package
• Ignore the actor packages (packages/actor-scraper/*) in oxlint — they're application code with their own bundler-specific tsconfigs; the shared scraper-tools library is still linted
• One source fix: drop unused err in web-scraper catch block
• One disable comment for an intentional generic param used only by a declaration-merged interface in scraper-tools/src/context.ts

Lint output

```
$ pnpm lint
Found 1 warning and 0 errors.
Finished in 143ms on 40 files with 117 rules using 14 threads.
```

(The single warning — `no-unsafe-optional-chaining` in scraper-tools — is pre-existing.)

Test plan

• `pnpm lint` — clean
• `pnpm format:check` — clean
• `pnpm test` — 16/16 passing
• `pnpm build` — all 8 turbo tasks succeed