Description of problem:
When using cockpit's "software update" tab, the "includepkgs" directive eventually defined in some repo is ignored. This can wreak havok on system where a thirdy party repository is enabled but filtered to provide only a very specific package subset. While cockpit is clearly affected by this problem, the root issue stems from PackageKit itself - which ignores the "includepkgs" directive.

Version-Release number of selected component (if applicable):
cockpit-packagekit-211.3-1.el8.noarch
PackageKit-1.1.12-4.el8.x86_64

How reproducible:
Enable a thirdy party repository which redefines some system package (eg: enable a fedora repository). While doing it repo-wide is clearly unwise, it can be very useful to reference only *some* packages via the "includepkgs" directive. However, clicking on the "check for update" button exposed in cockipit will lead to massive upgrades, which can wreak havoc on the entire system.

Steps to Reproduce:
1. enable a fedora repo with a specific "includepkgs" directive including a single packet
2. check that "yum update" will *not* propose a massive upgrade
3. the "check for update" button in cockpit *will* suggest upgrading 100s packages

Actual results:
Massive, dangerous upgrades are proposed

Expected results:
Only enabled/unfiltered packages should be proposed for the upgrade. More broadly, PackageKit should honor yum/dum directives as "includepkgs".

Additional info:
None