Description of Problem

• Notifications controller unable to send notifications, In v1.15.x. it was working fine and after update to `v1.16.1`[2.14.13] it stucks on sending notification and later doesn't process any other trigger and also don't show any error even after putting it in debug mode.
• Even tested using `v2.14.15` image but it didn't work. 

Additional Info

• Using `v2.13.1` image it works as expected.

Reproducibility

• Always

Prerequisites/Environment

• OpenShift GitOps 1.16.1

Steps to Reproduce

• Enable Notifications from ArgoCD CR
• add SMTP email service in NotificationsConfiguration CR
• add subscription for recipients to receive notifications in NotificationsConfiguration CR Or set notification annotation on Application
• Try triggering notification using trigger which used in last step with subscription or annotation.

Expected Results

• Mail received by recipient via SMTP mail server

Actual Results

• In logs, it stuck on sending notification and user doesn't get any email notification 

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

• <What is the root cause of the problem? Or, why is it not a bug?>

Workaround (If Possible)

• Use older ArgoCD version image, tested `v2.13.1`

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• ...

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.