fix: retain original request in middleware handler

[IdanLupinskyMyPorsche]

we noticed that custom headers from the original request were not retained as NextResponse.next was called without the original request

• All new/changed/fixed functionality is covered by tests (or N/A)
• [n/a] I have added documentation for all new/changed functionality (or N/A)

📋 Changes

This should be a fix to allow the original request to be retained when passed through the middleware. We require this to retain a custom header in the original request.

📎 References

🎯 Testing

As you can see we updated one of the tests handling a "no matching auth route" to see that the NextResponse.next was called with the original NextRequest. In particular, we tested that the request passed is the same using a spy.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.06%. Comparing base (fd6a68f) to head (770de96).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1919   +/-   ##
=======================================
  Coverage   76.06%   76.06%           
=======================================
  Files          20       20           
  Lines        1496     1496           
  Branches      233      233           
=======================================
  Hits         1138     1138           
  Misses        351      351           
  Partials        7        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tusharpandey13]

lgtm