fix(idlelogoutconfirmationmodal): Fixing an issue in the idle timer logic when query parameters are appended to the page

[blechner]

Closes #

Summary

• Fixing an issue in the idle timeout confirmation dialog where changes in the current url (like appending a query parameter) without reloading the page caused the idle timer to restart and enter an invalid state where the countdown dialog would show up frozen.

Change List (commits, features, bugs, etc)

• Assembling the originHref parameter to be added to the logout URLs in such a way that the current page's query parameters are not included. An easier solution would be to just remove originHref for good, since MAS is no longer using it, but we cannot assume that other consumers of the component aren't using it, so it is better to keep it in order to not introduce breaking changes.
• Adding a null check in surveyData to avoid runtime errors if this property becomes null in subsequent component re-renders.

Acceptance Test (how to verify the PR)

• When using the IdleLogoutConfirmationModal in a MAS application, reduce the idle timeout (to avoid having to wait 30 minutes), them run this in the development console to include an extra query parameter to the page url: window.history.replaceState(undefined, 'XXXX', window.location.href + "?tab=x"). Wait for the idle timeout dialog to pop up and notice that the countdown happens normally, i.e. should keep decreasing by 1s. No frozen countdown number is expected.

Regression Test (how to make sure this PR doesn't break old functionality)

• Some unit tests were adjusted and all of them are passing.

Things to look for during review

• Make sure all references to iot or bx class prefix is using the prefix variable
• (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
• UI should be checked in RTL mode to ensure the proper handling of layout and text.
• All strings should be translatable.
• The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
• Unit test should be written and should have a coverage of 90% or higher in all areas.
• All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
• Changes or new components should either write new or update existing documentation.
• PR should link and close out an existing issue

[netlify]

✅ Deploy Preview for carbon-addons-iot-react ready!

Name	Link
🔨 Latest commit	9b73ede
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-addons-iot-react/deploys/640f529208a30400078d07df
😎 Deploy Preview	https://deploy-preview-3750--carbon-addons-iot-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[herleraja]

LGTM

[davidicus]

In the future I would prefer a template literal here.

Suggested change

	[window.location.protocol, '//', window.location.host, window.location.pathname].join('')
	`${window.location.protocol}//${window.location.host}${window.location.pathname}`