Fix: Add --emit-translation-events to toggle creating of events in translation and config applying

[randmonkey]

What this PR does / why we need it:

Add --emit-translation-events to disable creation of events for successful config applies, translation failures and config apply failures in translation to prevent large amount of events to be a source of load to k8s API server.

Which issue this PR fixes:

fixes #5252.

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

• the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

[codecov]

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (e84786e) 75.8% compared to head (d478fde) 75.8%.
Report is 1 commits behind head on main.

Files	Patch %	Lines
internal/manager/run.go	50.0%	3 Missing and 1 partial ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #5296   +/-   ##
=====================================
  Coverage   75.8%   75.8%           
=====================================
  Files        170     170           
  Lines      19450   19457    +7     
=====================================
+ Hits       14753   14767   +14     
+ Misses      3864    3859    -5     
+ Partials     833     831    -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[team-k8s-bot]

The backport to release/2.12.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/2.12.x release/2.12.x
# Navigate to the new working tree
cd .worktrees/backport-release/2.12.x
# Create a new branch
git switch --create backport-5296-to-release/2.12.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8b3d551ea7c93048add583f517992e8a6883e7d7
# Push it to GitHub
git push --set-upstream origin backport-5296-to-release/2.12.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/2.12.x

Then, create a pull request where the base branch is release/2.12.x and the compare/head branch is backport-5296-to-release/2.12.x.

[team-k8s-bot]

The backport to release/3.0.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.0.x release/3.0.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.0.x
# Create a new branch
git switch --create backport-5296-to-release/3.0.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8b3d551ea7c93048add583f517992e8a6883e7d7
# Push it to GitHub
git push --set-upstream origin backport-5296-to-release/3.0.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.0.x

Then, create a pull request where the base branch is release/3.0.x and the compare/head branch is backport-5296-to-release/3.0.x.

[czeslavo]

Suggested change

	flagSet.BoolVar(&c.EmitTranslationEvents, "emit-translation-events", true, `Emit Kubernetes events for successful configuration applies, translation failures and configuration apply failures on managed objects.`)
	flagSet.BoolVar(&c.EmitKubernetesEvents, "emit-kubernetes-events", true, `Emit Kubernetes events for successful configuration applies, translation failures and configuration apply failures on managed objects.`)

I think the flag shouldn't include translation as it decides about emitting not only translation events.

[tao12345666333]

#5299 has been merged. Thanks