fix: update getFilenameFromUrl to return errorCode and filename

[bjohansebas]

Summary

I’m removing this TODO that was there. I still need to investigate whether the next TODO actually exists and fix it if so. Now that it returns other things, I think we should change the name, what do you think?

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

If relevant, what needs to be documented once your changes are merged or what have you already documented?

[codecov]

Codecov Report

❌ Patch coverage is 94.28571% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 95.67%. Comparing base (063213e) to head (6029167).
⚠️ Report is 1 commits behind head on next.

Files with missing lines	Patch %	Lines
src/middleware.js	93.75%	1 Missing ⚠️
src/utils/getFilenameFromUrl.js	94.44%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2253      +/-   ##
==========================================
- Coverage   95.85%   95.67%   -0.19%     
==========================================
  Files          13       13              
  Lines         892      901       +9     
  Branches      260      263       +3     
==========================================
+ Hits          855      862       +7     
- Misses         37       39       +2     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bjohansebas]

Moving back to draft because we need to use new URL() and stop using url.parse()

[bjohansebas]

Okay, for now one test is failing. When publicPath is defined, the behavior of using new URL is more different than I expected. We need to make sure it doesn’t imply additional changes, because new URL is not a direct replacement for url.parse.

[alexander-akait]

Refactored to use throw when we have real problems and return undefined when not found (or not parsable)

[alexander-akait]

Also I am thinking about union parse url and publicPath, less calls and faster, but we need extra checks here, all possible values - https://webpack.js.org/configuration/output/#outputpublicpath + broken cases