🌱 Scan webhook packages during manifest generation

[joshfrench]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Discovered while working on #5812: controller-gen's paths list omitted every */webhooks package, so no +kubebuilder:webhook markers were ever discovered. make generate never rewrote config/webhook/manifests.yaml, leaving it to be edited by hand.

Special notes for your reviewer:

This will incur a one-time reordering of manifests.yaml as controller-gen reorders entries from their accumulated manual order.

AI Usage:

Claude used to verify I'd caught the complete list of webhook dirs and that the diff in manifest.yaml is purely to entry order, no change to the actual webhook definitions.

Checklist:

• squashed commits
• includes documentation
• includes AI generated content
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:
NONE

[kubernetes-prow]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[kubernetes-prow]

Hi @joshfrench. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[faiq]

/ok-to-test