LV considers an internally computed MaxVF to decide if a constant trip-count is
a multiple of any subsequently chosen VF, and conclude that no scalar remainder
iterations (tail) will be left for FoldTail to handle. If an external VF is provided via
-force-vector-width, it must be considered instead of the internal MaxVF.
If an external UF is provided via -force-vector-interleave, it too must be
considered in addition to MaxVF or user VF.
Fixes PR45679.
It might be slightly better to have computeFeasibleMaxVF itself have a shortcut to return UserVF. That would potentially avoid missing the accounting for UserVF in new users of computeFeasibleMaxVF