Handle for invalid referer for embedded page service

[Philwi]

What? Why?

Closes #9355

In some cases the referer of the current url is invalid and not a valid url. In these cases the current behaviour throws an unhandled exception and the page could not been visit.

What should we test?

• I could not reproduce it in Chrome or in Firefox 👎

Release notes

Changelog Category: User facing changes

The title of the pull request will be included in the release notes.

[jibees]

This PR contains some commit (around packages upgrade) that shouldn't appear it. Could you please rebase/squash your PR? Thanks a lot! 🙏

[Philwi]

This PR contains some commit (around packages upgrade) that shouldn't appear it. Could you please rebase/squash your PR? Thanks a lot! pray

Yes, for sure! :)

[mkllnk]

Nice!

[filipefurtad0]

Hey @Philwi ,

Thanks - I could not reproduce the bug either.
I'm not sure how I could test your code change. I've deployed it, navigated around, typed in some incorrect URLs but as described in the issue, but yeah the browser (Firefox) corrected it. Also and using Browserstack tried it in Microsoft Explorer, but noticed nothing unusual.

From what I gather the PR adds a safeguard against incorrect URLs - provided we have them. Having nothing else to check I'd say this is good to merge. If something crosses your mind don't hesitate and do let me know 👍

Thanks again!