chore: adding test coverage for the notification_controller

[zhaque44]

Adding tests for the notifications_controller | controller package:

• Added two tests for the Init function.

This test helps ArgoCD users because:

• The Init function initializes various informers that the Notification Controller relies on for its functionality. If the informers fail to initialize, then the NotificationController will not be able to properly function, which would be problematic for ArgoCD users.
• It ensures that the Notification Controller is properly configured with the correct parameters, such as the Kubernetes client and informers, as well as the required labels and secrets/config maps. This is important because users of the package may be using it in different environments with different configurations, so it's important to ensure that the package is properly configured to function correctly in any environment.

Added test for getAppProj function.

• This test verifies that getAppProj gracefully handles missing field and returns nil when that happens.

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +0.04 🎉

Comparison is base (ceed653) 49.01% compared to head (c813ed3) 49.06%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #13339      +/-   ##
==========================================
+ Coverage   49.01%   49.06%   +0.04%     
==========================================
  Files         247      248       +1     
  Lines       42685    42810     +125     
==========================================
+ Hits        20924    21006      +82     
- Misses      19645    19684      +39     
- Partials     2116     2120       +4     

see 6 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[jannfis]

Thanks, appreciated!

LGTM.