Re-export url::ParseError alongside url::Url

[eyupcanakman]

Url::parse returns Result<Url, ParseError> and Error already has a From<url::ParseError> impl, but only Url is re-exported. Naming the error type means taking a direct dependency on url.

Re-exports it alongside Url (pub use url::{ParseError, Url};), with a trybuild pass test next to the start-handler.rs one from #974.

Adding ParseError at the root can conflict under use worker::* if chrono's ParseError is also in scope via *, though I didn't find a public crate doing that and an explicit import clears it. Given #890, I can re-export the url module for worker::url::ParseError instead if you'd prefer.

Closes #380.

[guybedford]

Thanks for the PR! I changed this to reexport url directly rather, so it becomes url::ParseError instead - clarifying the namespacing and better supporting further similar issues.

[codspeed-hq]

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

✅ 2 untouched benchmarks

---

_{Comparing eyupcanakman:reexport-url-parse-error (ca85855) with main (78dc0cd)}