fix: keep content-length header in compressed responses

[barjin]

Closes #388

[Copilot]

Pull request overview

This PR addresses issue #388 where Node.js binding responses were missing the content-length header for compressed responses, by updating dependencies and adding a regression test to ensure the header is preserved.

Changes:

• Add a Node integration test asserting content-length is present alongside content-encoding.
• Update the Node native binding loader’s expected package version to 0.9.2.
• Patch Rust dependency resolution to use an Apify fork of tower-http (affecting reqwest’s dependency graph) and update Cargo.lock accordingly.

Reviewed changes

Copilot reviewed 4 out of 6 changed files in this pull request and generated 2 comments.

File	Description
impit-node/test/basics.test.ts	Adds a regression test for content-length on compressed responses.
impit-node/index.js	Bumps the native binding package version check from 0.9.0 to 0.9.2.
Cargo.toml	Patches tower-http to an Apify git source (currently tracking main).
Cargo.lock	Locks tower-http to the selected git commit and updates transitive deps.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.