NR UI: users getting 403 when loading a bookmarked NR

**\* THIS IS AN ONLY AN IDEA FOR DISCUSSION. DO NOT IMPLEMENT AT THIS TIME.\* **

---

Even with the recent NR UI changes, some users are still experiencing a 403 (auth) error while fetching their NR. ([seen often in Sentry](https://sentry.io/organizations/registries/issues/2367173892/?project=5433955&query=is%3Aunresolved))

It was found that the user's keys (email address, phone number, NR number / NRL), which are supposed to be in session storage, may be null. As we have no evidence that these keys were not properly saved or restored in the user's current session, we instead believe that the user has bookmarked their NR page and is trying to restore that bookmark in a new session.

This proposal is to store the user's keys (email address, phone number, NR number / NRL) as URL parameters instead. This should not affect the usual flow from NR UI to PayBC and back, and it would allow users to bookmark their NR page.

Sample URL (not URL encoded here for legibility):
`https://www.bcregistry.ca/namerequest/?nrNum=NR 2163561&phoneNumber=250-555-1111&emailAddress=user@mail.com`

Potential downsides:
1. This proposal exposes the user's keys in the URL (instead of "hiding" them in the session storage).
2. If a user shares the URL with another user, then the other user will be able to open the NR (which is the same as the first user sharing the NR number and their email or phone).
3. If we implement this and then later remove it, users who had bookmarked their NR would no longer be able to fetch them with that URL.

This was discussed with Kial: [https://app.zenhub.com/files/157936592/db4551b2-29ad-40f6-ac60-7474ce84f0b2/download](https://app.zenhub.com/files/157936592/db4551b2-29ad-40f6-ac60-7474ce84f0b2/download)