Refactor WatchDeploymentLogs to use label selectors instead of selecting deployments by name.

[chrischdi]

User Story

As a developer I would like to call a function in e2e tests to stream logs of deployments, selected by a label selector, for not requiring to know the exact name of the deployment in the test implementation.

Detailed Description

Currently we do already the same but need to know the exact deployment name to do so, example: https://github.com/kubernetes-sigs/cluster-api/pull/6892/files .

Anything else you would like to add:

Follow up issue via comment:

I suggest also opening a follow-up issue so we can search for deployments with a well know label instead of relying on a well-known name. This will make the test helper usable by projects having different extensions names or for use cases where more than one extension is required [0]

/kind cleanup

[adilGhaffarDev]

I would like to work on it. I am assigning it to myself.
/assign

[fabriziopandini]

/triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[fabriziopandini]

/lifecycle frozen
/unassign @adilGhaffarDev
/help

[sbueringer]

/assign @adilGhaffarDev

/remove-help

given we have an open & active PR: #7039

(except if I'm missing something :))