Align type-definition style with Apify Coding Standards

[l2ysho]

While reviewing #1199 (#1199) (thread (#1199 (comment))) we noticed that oxlint.config.ts enforces:

'typescript/consistent-type-definitions': ['error', 'interface'],

This forces every type definition in the codebase to use interface, which conflicts with the Apify Coding Standards Guide (https://www.notion.so/apify/Apify-Coding-Standards-Guide-264f39950a2280588be3f2268b9cb609), which prefers type.

Proposed change

1. Flip the rule in oxlint.config.ts to ['error', 'type'] (or remove it if the shared @apify/oxlint-config already covers it).
2. Migrate existing interface declarations to type across the codebase (largely mechanical / autofixable).
3. Confirm alignment with @apify/oxlint-config — ideally the standard lives there as a single source of truth rather than being overridden per-repo.
4. Check if other custom rules in CLI oxlint config are aligned with Apify Coding Standards Guide