CLOUDP-313040: Fix DryRun

[helderjs]

Summary

In DRY RUN mode, AKOv2 does not emit Kubernetes events for operations that manage team associations with AtlasProject resources. This is caused by a bug where the underlying error is silently swallowed, preventing proper event reporting. As a result, users receive no indication that an action would have taken place. The expected behavior is that AKOv2 should surface these operations as Kubernetes events when in DRY RUN mode, to maintain full visibility of intended changes.

Proof of Work

Unit tests were added

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you checked for release_note changes?
• Have you signed our CLA?

Reminder (Please remove this when merging)

• Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
• Remember the following Communication Standards - use comment prefixes for clarity:
  • blocking: Must be addressed before approval.
  • follow-up: Can be addressed in a later PR or ticket.
  • q: Clarifying question.
  • nit: Non-blocking suggestions.
  • note: Side-note, non-actionable. Example: Praise
  • --> no prefix is considered a question