Label-Based resource ownership - ALB and Certificates

[meneksece]

How to categorize this PR?

What this PR does / why we need it:

This PR introduces structured ownership for Application Load Balancer (ALB) and Certificate resources. By using a consistent labeling system based on the IngressClass UID, the controller can now easily find and clean up the resources of ALB and Certificate it created.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Key Changes:

Ownership Labeling: Introduced LabelIngressClassUID (prefixed with alb-ingress-controller-) to track resource provenance.

Label Addition: Added logic in getAlbSpecForResources to include the ownership label to the alb spec.

Extended Interface: Updated applyCertificates to accept the IngressClass object to ensure certificates are also labeled upon creation.

Breaking changes:

-->

[ske-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 kumm-kai 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

[ske-prow]

@meneksece: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cloud-provider-stackit-verify	4eb2b4e	link	true	/test pull-cloud-provider-stackit-verify

Full PR test history. Your PR dashboard. Command help for this repository.
Please help us cut down on flakes by linking this test failure to an open flake report or filing a new flake report if you can't find an existing one. Also see the gardener testing guideline for how to avoid and hunt flakes.

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. I understand the commands that are listed here.

[kamilprzybyl]

I'd just delete this file entirely, it's commented out and test cases are outdated

[meneksece]

I'd like to keep it since we are planning soon to re-introduce them, even though some tests are outdated, the setup will be helpful instead of starting over.