chore: sync .NET client with Apify OpenAPI spec v2-2026-07-07T132551Z

[Pijukatel]

Summary

Syncs the .NET client to the latest Apify OpenAPI specification, info.version = v2-2026-07-07T132551Z (131 paths / 229 operations), up from v2-2026-07-02T131926Z.

An independent endpoint- and parameter-level audit of the current spec against the client confirmed no in-scope API surface change — full parity with the reference JS client holds (all 27 resource clients covered, validateInput present and consistent, browser-info/tools/* correctly out of scope). This is a no-behavior-change version rebuild plus documentation corrections.

Changes

• Bump ApiSpecVersion → v2-2026-07-07T132551Z (ApifyClientVersion.cs) and project <Version> 0.1.0 → 0.1.1.
• Correct the LastRunOptions doc comment: the 07-07 spec now declares Origin (alongside Status / waitForFinish) as a query parameter on the last-run endpoints. No behavior change — the client already sent origin. waitForFinish remains correctly not exposed on lastRun, matching the reference JS lastRun({ status, origin }).
• List previously-omitted types (StreamedLog, DownloadItemsFormat, NestedWebhookCollectionClient, WebhookDispatchCollectionClient) in the docs/README.md namespace table.
• Add the missing ChargeAsync return-type arrow in docs/runs.md.
• Add CHANGELOG.md 0.1.1 entry.

Verification

• Reviewed independently against the authoritative spec; all review items closed. Note: the .NET SDK is not available in the sync environment, so build/format/test gates run on this PR's CI rather than locally — the change is otherwise a version constant + documentation edits.

---

Generated by Claude Code