Remove skipping logic in PL CI

[akihironitta]

What does this PR do?

[hotfix] Fixes #14564.
Partially redo #14170 but for a different reason stated in the above issue.

The impact coverage is only PL, so I'm adding this PR to 1.7.x milestone.

Does your PR introduce any breaking changes? If yes, please list them.

None

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• [n/a] Did you make sure to update the documentation with your changes? (if necessary)
• [n/a] Did you write any new necessary tests? (not for typos and docs)
• [n/a] Did you verify new and existing tests pass locally with your changes?
• [n/a] Did you list all the breaking changes introduced by this pull request?
• [n/a] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

cc @tchaton @rohitgr7 @carmocca @akihironitta @Borda

[carmocca]

LGTM, but this will increase the burden of app development until #14294 is finished. Hopefully within this week. This is because these jobs are marked as required so they cannot be skipped with a path filter.

[awaelchli]

but this will increase the burden of app development until

Should we maybe merge #14294 and this one together on the same day when both are ready?