Excluding snapshot tests, there are 166 instances of "pf-5" that remain in the codebase. There are three specific tickets for repeat offenders, and there are 103 remaining scattered across many classes and CSS vars. This ticket is a catch all to deal with them.

We should, if at all possible, lean towards deleting pf-v5 instances found in css files rather than attempt to migrate to an alternative. If we can pinpoint what and where the rules are targeting, we should evaluate if the PatternFly default styling is good enough, or if there is an alternative that does not involve overriding default styles. This will greatly ease the migration to PatternFly 6 if our experience with 4->5 and 5->6 is any indication.