Bug 2360183

After the update to f42 restorecon doesn't seem to correctly label files when a local context is defined for them.

I face the problem with cloud-init as I try to relabel that to bin_t.

Reproducible: Always

Steps to Reproduce:
1. dnf in cloud-init
2. semanage fcontext --add --type bin_t /usr/bin/cloud-init
3. restorecon -v /usr/bin/cloud-init
4. ls -Z /usr/bin/cloud-init
Actual Results:
The cloud-init binary is still labelled cloud_init_exec_t


Expected Results:
The cloud-init binary should be labelled bin_t like it is on f41.

Additional Information:
# rpm -q policycoreutils
policycoreutils-3.8-1.fc42.aarch64

# semanage fcontext -l | grep cloud-init
/etc/NetworkManager/dispatcher\.d/cloud-init-azure-hook regular file       system_u:object_r:NetworkManager_dispatcher_cloud_script_t:s0 
/run/cloud-init(/.*)?                              all files          system_u:object_r:net_conf_t:s0 
/usr/bin/cloud-init                                all files          system_u:object_r:bin_t:s0 
/usr/bin/cloud-init                                regular file       system_u:object_r:cloud_init_exec_t:s0 
/usr/lib/systemd/system-generators/cloud-init.*    all files          system_u:object_r:cloud_init_exec_t:s0 
/usr/lib/systemd/system/cloud-init.*               regular file       system_u:object_r:cloud_init_unit_file_t:s0 
/var/log/cloud-init.*\.log.*                       regular file       system_u:object_r:cloud_log_t:s0