Session timeout on page with read requests

[jrchudy]

This requires further discussion and is related to issue #1838 .

The scenario is that a timeout/logout occurred while a user was looking at a page that can trigger further read requests (record/recordset) that require certain permissions to retrieve the data.

The user loaded the page with permission to see the content, a timeout (or logout) occurs, then the user tries to facet (recordset) or page to the next page of data or change the page size (record/recordset). The user is then prompted with a login modal:

1. The same user signs in again
   - we take a similar approach as we are doing for recordedit and continue processing the requests that previously caused an error (post login)
2. A different user signs in, this user does NOT have permission to read the table an action was taken on
   • error modal shown to user with appropriate error message, do not allow dismissal and provide a "reload" and "home" navigation option
   • Alternative (HT):
     • error message: Your login account xxx is different from the existing account.
     • Click OK to continue with account xxx. Continue as xxx will refresh the page with new credential. Dismiss will leave them where they were.
   • @RFSH suggested that not having permission could also be an issue with a pseudo column which touches a table the user can't read from. Not sure if this changes how this should be handled
3. A different user signs in, this user does have permission to read the table an action was taken on
   • should this be handled like the above case for a user without permission?
4. A different user signs in, this user has MORE permissions to read the table an action was taken on
   • This means the user could have more columns visible to them that aren't being shown
   • Same could happen with a user with less privileges, they may not be able to see a specific set of columns shown
5. The user returns to an anonymous user without logging back in
   • facet popups may have less options visible to them and not be aware of being logged out and why the options seem to be less than usual

The current functionality is to automatically reload the page when a user logs in. This was done to simplify the process and not have to worry about handling it differently.

This is related to issue #1918 .

@karlcz @hongsudt could you review this and add comments?