Bump srvx from 0.8.9 to 0.11.13

[dependabot]

• Inspect the previous srvx upgrade commit and current branch state
• Investigate recent CI/build failures for this PR
• Reproduce the build/test failure locally
• Make the smallest code changes needed for srvx 0.11.13 compatibility
• Run targeted validation and final checks
• Reply to the PR comment with the addressing commit hash

[changeset-bot]

⚠️ No Changeset found

Latest commit: ebc738e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	srvx@​0.8.9 ⏵ 0.11.13	+1	+2	-3	+1

View full report

[Murderlon]

@copilot fix the build errors that were introduced by upgrading srvx

[Copilot]

@copilot fix the build errors that were introduced by upgrading srvx

Addressed in ebc738e. The srvx 0.11 upgrade now builds again by narrowing toNodeHandler() to the HTTP/1 request/response types used by server.handle(), and I updated the preserved-request test to use a real Node HTTP server because the old mock response no longer matches srvx’s expectations. I also re-ran npm run build, npm run format:check, npm run lint, and the server-focused test suite successfully.