Handle %generate_buildrequires differences between dnf and dnf5
    
    There seems to be differences in how %generate_buildrequires works
    between recent dnf and dnf5 versions, resulting in the rm command
    trailing %pyproject_buildrequires sometimes not being run, causing
    the subsequent cycle to fail in the ln command due to the symlinks
    already existing from the previous cycle.  Instead, proactively
    remove the symlink targets; it shouldn't matter if they remain during
    the %build stage and beyond.