DIGITAL-732 - Update autologout to 2.0.3 and add our updated patch

[arpage]

Jira ticket

DIGITAL-732

Purpose

Fix issues present in the new 2.0.3 patch, with timeout handling in multiple tabs.
Incorporate the existing 2.0.3 patch, and layer our changes on top.

Deployment and testing

Local Setup

Running lando rebuild may be in order as we've updated the autlogout module, and added a patch for it as well.

QA/Testing instructions

Ensure CMS auto logout still works:

• Deploy locally
• Open another tab in a separate window, so you can see the current admin page, and another admin page (e.g. Content)
• Go to the admin modules listing, and search for autologout
• Confirm the version is 2.0.3, then click Configure
• Set each of the two timeout values (which are currently set to 1800 seconds) to 90 seconds, and save the config.
• Do nothing in either window/tab for 90 seconds, and you should see each window/tab show an Alert modal, asking if you want to reset the session.
• Click Yes, and the modal should disappear on the current window/tab
• Within 20-ish seconds the modal should disappear on the other window/tab
• Both windows/tabs should remain logged in, and allow you to perform admin tasks.
• After confirming this works, remain idle in both windows/tabs for another 90 seconds until you see the modal alerts again.
• This time don't click on either of them for 20 seconds
• After this interval, both windows/tabs should be logged out of the cms

Testing Process Screenshots:

Note the screenshots are for USA.gov, but the functionality is exactly the same

• Autologout config page:
• Single Tab Modal Alert:
• Multi-tab Modal Alert:

Checklist for the Developer

• A link to the JIRA ticket has been included above.
• No merge conflicts exist with the target branch.
• Automated tests have passed on this PR.
• A reviewer has been designated.
• Deployment and testing steps have been documented above, if applicable.

Checklist for the Peer Reviewers

• The file changes are relevant to the task objective.
• Code is readable and includes appropriate commenting.
• Code standards and best practices are followed.
• QA/Test steps were successfully completed, if applicable.
• Applicable logs are free of errors.