file and dir dependencies: mention explicit path dependencies, reorder
    
    The text is inverted, to list the allowed uses first, and then to exclude the
    unwanted ones.
    
    The text didn't mention the case where one package has an explicit
    Provides:/some/path and another package uses
    Requires|Recommends|Suggests:/some/path. Those explicit Provides are included in
    the primary metadata and can be used with no problem and they are sometimes
    useful to coordinate functionality between packages.
    
    Also, with dnf5 the split between "primary" and "filelists" metadata matters
    again, and the latter is not dowloaded by default. So reword the explanation
    a bit to discourage packagers from using it.
    
    The rule is extended to also cover directories. I suspect that the omission was
    just clumsy language and not intentional.