Description of problem:
We (subscription-manager team) are working to change how subscription-manager collects network facts, making use of `ip` from the iproute package. When a first draft of the change was tested with QE's help, the result was that rhsmcertd-worker (spawned by rhsmcertd) does now allow this execution -- for example:

type=AVC msg=audit(1684773208.054:13797): avc:  denied  { execute } for  pid=57312 comm="rhsmcertd-worke" name="ip" dev="vda1" ino=12803826 scontext=system_u:system_r:rhsmcertd_t:s0 tcontext=system_u:object_r:ifconfig_exec_t:s0 tclass=file permissive=0

The `ip` usage seems to not trigger denials when run from the subscription-manager CLI, e.g. when registering using `subscription-manager register` or a simpler `subscription-manager facts` (to trigger the facts collection).

Hence, please allow rhsmcertd-worker to execute/run `ip`.

How reproducible:
All the time.

Steps to Reproduce:
1. Install a version of subscription-manager that uses `ip` to collect network facts
2. Shorten the check-in time of rhsmcertd to e.g. 5 minutes & disable the splay (the randomization of the check-in time within the interval), so you can see the problem quicker than waiting for the default check-in time (which is ~4h):
  # subscription-manager config --rhsmcertd.certCheckInterval=5 --rhsmcertd.splay=0
3. Restart rhsmcertd: `systemctl restart rhsmcertd.service`
4. Register a system: `subscription-manager register`
5. Wait for 5 minutes

Actual results:
SELinux denials for the execution of "ip" as shown above.

Expected results:
No denials.