Issue Summary

Switching between two add-on project pages results in outdated context parameters in NAV4.

This is an issue on connect and connect on forge apps having `jiraProjectPages` module as:

onnectModules:
    jira:jiraProjectPages:
    - url: ...&projectKey={project.key}&selectedSi={ac.selectedSi}
      name:
        value: ...
      key: ...

Steps to Reproduce

1. Install an app with jiraProjectPages like The Scheduler from the marketplace
2. Create two projects in the instance, one of them has to be a service project
3. From the first project, and with the network tab opened, load the app, check the request that starts with for the payload value:
   1. https://mycompany.com/jira-template/projects/10068/scheduled-issues?descriptorVersion=……
   2. It will retrieve the correct project.key from the context
4. Now, go to the app in the service project via the project tree (left vertical Jira bar), and check for the request that follows the same structure from above for its payload.
   1. It will have the previous project key, instead of the new one.
   2. That way is necessary to reload the page to receive the correct project.key
   3. It also correctly gets the project.key from the context when you are previously in one of the service project pages, like from summary to the app (in the same project).

Expected Results

Context to have the new selected project key.

Actual Results

Request is sent with the old project key.

Workaround

Refresh the page.