test if fapolicyd can create /var/lib/rpm/.dbenv.lock
    
    Recent testing of the fapolicyd service revealed that the service
    wants to write to /var/lib/rpm directory and create .dbenv.lock
    file there. This action was denied by SELinux because the SELinux policy
    brought by fapolicyd is missing an appropriate rule.
    
    I believe this access should be allowed because the fapolicyd service
    uses a rpmdb backend which is responsible for such activity.
    
    The automated TC checks if appropriate policy rules are present, but it
    does not reproduce the issue (it only appears during a reboot).
    
    The TC covers BZ#1876538.