feat: Zod-based Configuration extending Crawlee's new approach

[B4nan]

Summary

Refactors the Configuration class to use Zod-based field definitions, extending Crawlee's new Configuration class cleanly without monkey patching.

• Uses crawleeConfigFields spread with Apify-specific overrides and additions
• Each field defines schema and env var aliases in one place
• Supports multiple env var aliases per field (e.g., ACTOR_ID, APIFY_ACTOR_ID)
• Removes all monkey patching of CoreConfiguration
• Adds zod as direct dependency

Before (with monkey patching)

// Old approach - monkey patching CoreConfiguration
CoreConfiguration.getGlobalConfig = Configuration.getGlobalConfig;
CoreConfiguration.ENV_MAP = Configuration.ENV_MAP;
CoreConfiguration.INTEGER_VARS = Configuration.INTEGER_VARS;
CoreConfiguration.BOOLEAN_VARS = Configuration.BOOLEAN_VARS;
CoreConfiguration.DEFAULTS = Configuration.DEFAULTS;

After (clean extension)

export const apifyConfigFields = {
    ...crawleeConfigFields,
    
    // Override with additional env var aliases
    defaultDatasetId: field(z.string().default('default'), {
        env: ['ACTOR_DEFAULT_DATASET_ID', 'APIFY_DEFAULT_DATASET_ID', 'CRAWLEE_DEFAULT_DATASET_ID'],
    }),
    
    // Add new Apify-specific fields
    token: field(z.string().optional(), { env: 'APIFY_TOKEN' }),
    actorId: field(z.string().optional(), { env: ['ACTOR_ID', 'APIFY_ACTOR_ID'] }),
};

export class Configuration extends CrawleeConfiguration<ApifyConfigFields, ...> {
    static override fields = apifyConfigFields;
}

Dependencies

Requires: apify/crawlee#3387

Test plan

• Type checking passes (after Crawlee PR is merged/published)
• Full test suite
• E2E tests

🤖 Generated with Claude Code