fix(service-worker): registration failed on Safari - #31140

I tried to rerun the CI as the errors that showed up seem no longer present on the lastest master. If that doesn't help @H--o-l can you please rebase your PR on top of the most recent master and forcepush to this branch?

git fetch upstream
git rebase upstream/master
git push --force-with-lease

thanks!

@IgorMinar CI looks good now, thanks!

@gkalpak I just amend the commit with both improvements. Don't hesitate to tell me if their is anything else.

^^ 🤞

@IgorMinar @gkalpak Hello!
I'm not familiar with the PR workflow, do I need to do something on the PR for it to be merge-able?
Or you guys are on it?

@H--o-l, can you please update the commit message to not contain [b3dda0e] and [b3dda0e]: b3dda0e but just b3dda0e (then ping me to mark the PR for merging)? I.e.:

fix(service-worker): registration failed on Safari

Since Angular v8, and commit b3dda0e, `parseUrl()` can be called without
`relativeTo`, thus `new URL()` can be called with `relativeTo = undefined`.

Safari does not like it and the service worker registration fails:
```js
new URL('https://angular.io/') // OK
new URL('https://angular.io/', undefined) // TypeError
```

Closes #31061

@gkalpak Oh ok, since you accepted the PR in the same time you made the remark, I believed it was not mandatory.
I just fix the commit message and rebase the branch, thanks!

Sorry for the confusion, @H--o-l. I approved it, but added the cleanup label; this was my (confusing) way of saying "This basically looks good to me, except for this one minor thing.".
I'll make sure I make that more explicit in the future.

I marked the PR for merging. Thx, again, for working on this ❤️

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}