fix: notifications successfully never timeout with included flag

[mlaurencin]

Description of Change

Closes #22192

This PR is fixing the bug that was appearing in using the timeoutType='never' option when creating a Windows toast notification. Before the notification was still disappearing after about 7 seconds of being on the screen. This fix adds a "Close" button to the notification, which causes the scenario='reminder' attribute of the notification XML to be respected and the notification to never timeout. This attribute is only respected when a button is present on the notification XML.

Before:

After:

cc @codebytere

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed an issue where Windows notifications with timeoutType of 'never' did not work properly.

[codebytere]

This looks great! Just one comment about localization.

[codebytere]

🥳

[ckerr]

LGTM. Thanks!

[release-clerk]

Release Notes Persisted

Fixed an issue where Windows notifications with timeoutType of 'never' did not work properly.

[trop]

I was unable to backport this PR to "11-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I was unable to backport this PR to "10-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I was unable to backport this PR to "9-x-y" cleanly;
you will need to perform this backport manually.

[trop]

@mlaurencin has manually backported this PR to "9-x-y", please check out #25862

[trop]

@mlaurencin has manually backported this PR to "11-x-y", please check out #25902

[trop]

@mlaurencin has manually backported this PR to "10-x-y", please check out #25926