[release-0.4] OU-803: Backport filter bar to PatternFly 5

[andreasgerstmayr]

I cherry-picked all recent changes and adapted them to PatternFly 5, to support OCP 4.15 - OCP 4.18. The diff of release-0.4 with main branch is now fairly small, making future backports easy.

For the PR review it's probably sufficient to look at the last commit (Revert PF6 changes) only, which shows the diff of PF5 (release-0.4 branch) and PF6 (main branch) changes.

[openshift-ci-robot]

@andreasgerstmayr: This pull request references OU-803 which is a valid jira issue.

In response to this:

I cherry-picked all recent changes and adapted them to PatternFly 5, to support OCP 4.15 - OCP 4.18. The diff of release-0.4 with main branch is now fairly small, making future backports easy.

For the PR review it's probably sufficient to look at the last commit (Revert PF6 changes) only, which shows the diff of PF5 (release-0.4 branch) and PF6 (main branch) changes.

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 openshift-eng/jira-lifecycle-plugin repository.

[jgbernalp]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreasgerstmayr, jgbernalp

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 [jgbernalp]

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

[andreasgerstmayr]

/label ux-approved
same ux changes as in main branch
/label qe-approved
qe will be done post merge

[openshift-ci-robot]

@andreasgerstmayr: This pull request references OU-803 which is a valid jira issue.

In response to this:

I cherry-picked all recent changes and adapted them to PatternFly 5, to support OCP 4.15 - OCP 4.18. The diff of release-0.4 with main branch is now fairly small, making future backports easy.

For the PR review it's probably sufficient to look at the last commit (Revert PF6 changes) only, which shows the diff of PF5 (release-0.4 branch) and PF6 (main branch) changes.

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 openshift-eng/jira-lifecycle-plugin repository.

[andreasgerstmayr]

/test upstream-amd64-aws-e2e

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD ba44250 and 2 for PR HEAD 2d378c3 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD ba44250 and 2 for PR HEAD 2d378c3 in total

[etmurasaki]

@IshwarKanse I've tested this using quay.io/rh-ee-emurasak/distributed-tracing-console-plugin:andreaspf5 consuming this PR and didn't find any major issue.
Questions and findings logged in this thread: https://redhat-internal.slack.com/archives/C03EPFR2BAR/p1747336839704279?thread_ts=1747237642.387239&cid=C03EPFR2BAR

Feel free to retest it with all backend knowledge, since I covered only UI side. Thanks!

[IshwarKanse]

/override ci/prow/upstream-amd64-aws-e2e

[openshift-ci]

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e

In response to this:

/override ci/prow/upstream-amd64-aws-e2e

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.