refactor: add ArgumentValidationError to @crawlee/core

[B4nan]

Adds a shared ArgumentValidationError (exported from @crawlee/core via errors.ts) for schema (zod) validation failures.

• message — a plain, human-readable sentence naming the offending field and the value it received, e.g. Invalid string: must match pattern /^[A-Z]{2}$/ at `countryCode`, got `CZE` . Not a JSON dump.
• issues — the structured zod issues, exposed directly on the error so consumers can branch on them without digging into cause.
• cause — the original ZodError, kept for completeness.

The constructor takes (error: ZodError, value: unknown) and formats the message itself (the value is walked by each issue's path to surface the offending value).

Why

This is the foundation for migrating Crawlee's argument validation from ow to zod. The Apify SDK has just done the same migration and currently defines this class itself (apify-sdk-js#636) — once this lands and releases, the SDK will re-export it from @crawlee/core instead, so the two stay in lockstep.

Scope is intentionally just the error class (+ its formatter and a test) — no ow call sites are migrated here.

@crawlee/core already depends on zod; built in dependency order + lint + the new test all pass.

🤖 Generated with Claude Code

[B4nan]

Now I realized we wanted to drop this SDK<->crawlee dependency, but even in that case, we want the same error handling experience (as well as zod instead of ow), so I'd merge this in regarldess.

[janbuchar]

Now I realized we wanted to drop this SDK<->crawlee dependency, but even in that case, we want the same error handling experience (as well as zod instead of ow), so I'd merge this in regarldess.

Agreed, but maybe we could put this in a package smaller than core? If SDK ends up depending on utils, for instance, nobody will bat an eye...

[B4nan]

We might want to take a closer look at this, and maybe even introduce some @crawlee/common package for that. The utils one has some deps we might not want in the SDK.