ROU-11512: notification - Unexpected behavior when using Notification with CloseAfterTime

[JoaoFerreira-FrontEnd]

This PR is to guarantee the autoclose of Notification works and respects the waiting time configured by the developer

What was happening

• When the notification was configured with CloseAfterTime, and the user interrupted this logic via API or interaction, the timeout triggering the close was not clean. This was causing an issue once the notification was triggered again. At that moment the old timeout could continue and close the notification without respecting the CloseAfterTime time that should be refreshed in every opening.

What was done

• add logic to clean Notification autoclose timeout every time the user closes the notification.

Test Steps

1. Go to Sample
2. Config Notification to CloseAfterTime 5000
3. Trigger and Close the notification repeatedly
4. After a few cycles trigger it and wait for the auto close
5. The notification should close after the intended timeframe.

Checklist

• tested locally
• documented the code
• clean all warnings and errors of eslint
• requires changes in OutSystems (if so, provide a module with changes)
• requires new sample page in OutSystems (if so, provide a module with changes)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud