pkg/webhook: log mutating handlers in OverridePolicy, ClusterPropagationPolicy, and MultiClusterService

[mohamedawnallah]

Description

In this commit, we log the mutating handlers for OverridePolicy, ClusterPropagationPolicy, and MultiClusterService. Specifically, it logs information about the mutation of these resources, including the namespace, name, and the operation type from the admission request.

Motivation and Context

During testing of the multi-cluster service webhook (#5517), I observed that all mutating webhook handlers include logging functionality, except for the handlers related to OverridePolicy, ClusterPropagationPolicy, and MultiClusterService. Adding logging to these handlers will improve debugging and enhance visibility into the operations they handle, which is the purpose of this PR.

What type of PR is this?

/kind feature

Does this PR introduce a user-facing change?:

Log mutating webhook handlers for OverridePolicy, ClusterPropagationPolicy, and MultiClusterService webhooks.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 32.45%. Comparing base (32c2ef7) to head (7506097).
Report is 22 commits behind head on master.

Files with missing lines	Patch %	Lines
pkg/webhook/clusterpropagationpolicy/mutating.go	0.00%	1 Missing ⚠️
pkg/webhook/multiclusterservice/mutating.go	0.00%	1 Missing ⚠️
pkg/webhook/overridepolicy/mutating.go	0.00%	1 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5521      +/-   ##
==========================================
+ Coverage   31.70%   32.45%   +0.75%     
==========================================
  Files         643      643              
  Lines       44445    44500      +55     
==========================================
+ Hits        14090    14443     +353     
+ Misses      29325    28963     -362     
- Partials     1030     1094      +64     

Flag	Coverage Δ
unittests	32.45% <0.00%> (+0.75%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[mohamedawnallah]

Closing and reopening some flaky e2e test failures...

[liangyuanpeng]

Closing and reopening some flaky e2e test failures...

/ok-to-test
then you can comment /retest to rerun github workflow

[mohamedawnallah]

/ok-to-test
then you can comment /retest to rerun github workflow

Thanks! Will try it next time instead of closing and reopening :)

[mohamedawnallah]

/retest

[XiShanYongYe-Chang]

Thanks~
/kind cleanup
/lgtm
/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: XiShanYongYe-Chang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [XiShanYongYe-Chang]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mohamedawnallah]

Closing and reopening some flaky e2e test failures...

/ok-to-test then you can comment /retest to rerun github workflow

@liangyuanpeng I've tried /ok-to-test and /retest/ and it gives me this error as you see here #5497 (comment):

@mohamedawnallah: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Any thoughts?