next.js

26bf7344 - fix: handle parsing destination with patterns in hostname (#75973)

fix: handle parsing destination with patterns in hostname (#75973) This handles when the rewrite destination is not a valid URL (as it's a pattern anyways, containing characters like `:` for patterns like `:subdomain.google.com` which wouldn't be valid). This uses the existing escaping behaviour to extract the url parts. Fixes https://github.com/vercel/next.js/issues/75956