Issue Summary:

Using Content Byline item, where the title and other information are dependent on https://developer.atlassian.com/cloud/confluence/context-parameters/ is not correctly loading when you revisit a page that was previously visited during navigation.

In addition to showing incorrect byline information, the byline action link is also incorrect. Clicking the byline link opens the target dialog on the wrong page.   

This is a significant problem for any application where the user interacts with the byline to work with the page.  For example, if the byline for page Alpha is shown on page Beta, when the user clicks the byline on page Beta, the modal dialog that opens thinks the user is on Alpha.   So if the user performs an action on the page, like Approval or a status change,  that action is actually applied to the wrong page.  

When this bug occurs after page navigation, the context information within the JWT security token generated and passed to any app will also be wrong. The context.confluence.content.id will refer to one of the previous pages, not the actual page in context.

This introduces a security problem when the trusted JWT context ID is used to verify user access to a page.

Steps to Reproduce

1. Have a Connect on Forge App using the referred module
2. Visit a page where the module is present
3. Visit another page where the module is present
4. Visit the page from step 2
5. Observe that the information is not loaded correctly, and it takes the information from step 3

Expected Results

It should load the correct context when you navigate between pages

Actual Results

When you revisit a page, the context is not reloaded; it is inherited from the previous page.

Workaround

Hard reload the page