feat: Node.js SDK update for version 25.1.0

[premtsd-code]

This PR contains updates to the Node.js SDK for version 25.1.0.

Changes

• Added sizeActual property to file model for actual stored size after compression
• Added Deno121, Deno124, and Deno135 runtime options to BuildRuntime and Runtime enums
• Updated advisor authentication examples to use API key instead of session
• Updated billing limits properties to be optional in project models

[greptile-apps]

Greptile Summary

This PR bumps the Node.js SDK to version 25.1.0, adding new model fields, runtime enum entries, and correcting advisor documentation examples.

• sizeActual field: Added as a required property on the File model (after sizeOriginal), with corresponding test fixtures updated in storage.test.js.
• BillingLimits optionality: billingLimits on Project and all eight fields inside BillingLimits are made optional; 16 test fixtures in project.test.js drop the now-unnecessary billingLimits: {} entry.
• Deno runtimes: Deno121, Deno124, and Deno135 added to both BuildRuntime and Runtime enums; advisor example docs switch from .setSession('') to .setKey().

Confidence Score: 5/5

This PR is safe to merge — all changes are additive model updates, enum extensions, and doc corrections with consistent test coverage.

All changes are mechanical SDK updates tied to the 25.1.0 server release: a new required field on the File model (backed by updated fixtures), optional-ifying billing fields that the server no longer guarantees, three new Deno enum entries, corrected advisor auth examples, and version string bumps. Each change has matching test updates and nothing touches control flow or security-sensitive paths.

No files require special attention.

Important Files Changed

Filename	Overview
src/models.ts	Added required sizeActual to File model; made billingLimits on Project and all BillingLimits fields optional — intentional per PR description
src/enums/build-runtime.ts	Added Deno 1.21, 1.24, and 1.35 enum members before the existing 1.40/1.46/2.0 entries
src/enums/runtime.ts	Mirrors build-runtime.ts change — added Deno 1.21, 1.24, 1.35 in the same position
src/client.ts	Version string bumped from 25.0.0 to 25.1.0 in both user-agent and SDK headers
test/services/storage.test.js	Added sizeActual: 12345 to three file fixture objects to match the new required model field
test/services/project.test.js	Removed billingLimits: {} from 16 test fixtures, consistent with making the field optional in the Project model
docs/examples/advisor/get-insight.md	Switched authentication example from .setSession('') to .setKey('<YOUR_API_KEY>')

_{Reviews (2): Last reviewed commit: "feat: update Node.js SDK to 25.1.0" | Re-trigger Greptile}

[greptile-apps]

Older Deno versions inserted mid-enum

deno-1.21, deno-1.24, and deno-1.35 are added before the already-existing deno-1.40, deno-1.46, and deno-2.0 entries. Were these legacy runtimes newly enabled in the Appwrite 25.0.1 server release, or is this a backfill that was accidentally omitted from earlier SDK versions? Confirming intent helps reviewers of any downstream SDK parity checks.

[greptile-apps]

Same older Deno versions inserted before newer entries

The Runtime enum mirrors the BuildRuntime change — deno-1.21, deno-1.24, deno-1.35 land before deno-1.40. If this is intentional (server 25.0.1 newly enables these legacy Deno targets), a brief note in the CHANGELOG entry would clarify why older versions are appearing in a minor bump.

[ChiragAgg5k]

LGTM. Auto-generated SDK updates consistent with the matching PRs in the other language SDKs (sizeActual on File, BillingLimits optional, Deno 1.21/1.24/1.35 added, advisor docs switched to API key auth, version + changelog bump).