JS SDK v2 scrape() rejects the zeroDataRetention option

The API accepts top-level zeroDataRetention on POST /v2/scrape, and the JS SDK already supports it on startCrawl() and startBatchScrape() — but scrape() has no such option in ScrapeCallOptions, so TypeScript users get a compile error (TS2353) when they try to use it:

await firecrawl.scrape(url, { zeroDataRetention: true });
// error TS2353: 'zeroDataRetention' does not exist in type 'ScrapeCallOptions'

Anyone needing zero data retention for single scrapes has to fall back to an as any cast. The option should be accepted and sent as a top-level payload field, same as crawl and batch scrape.