feat: harden next-api-bridge for 0.1.7

[Alidantech]

Summary

Prepares next-api-bridge 0.1.7 for production use while preserving createNextApiBridge() and the existing get, post, patch, put, and delete methods.

Implemented:

• serializable response metadata and safe response-header allowlisting
• secure browser request-context forwarding and generated request IDs
• trusted Vercel, Cloudflare, and custom-proxy client IP resolution
• approved client-origin forwarding
• redacted structured logging
• hardened cookie synchronization and policy rewriting
• eager configuration validation
• corrected URL, query, cache, timeout, abort, and custom-header behavior
• unit, integration, packed production Next.js E2E, tarball, Node 20/22, and Next 15/16 release gates
• 0.1.6 migration documentation

Verification completed

The full release verifier passed on:

• Node 20 + Next.js 15
• Node 20 + Next.js 16
• Node 22 + Next.js 15
• Node 22 + Next.js 16

Every matrix job passed strict TypeScript, unit tests, integration tests, build, tarball export verification, and packed production Next.js/Playwright E2E tests.

The temporary release archive and installer workflow have been removed. The final branch includes the clean source, tests, documentation, permanent CI workflows, and synchronized 0.1.7 package lock.

Release safety

This pull request does not publish or merge the package. Publishing remains gated by the release workflow and prepublishOnly checks.