Provides with Conflicts are incorrectly reported as in cyclic dependency
Packages that provide and conflict with some other package are reported as being in cyclic dependency with that package. This is because we are for sure following provides as a dependency and simply if it leads back to package it self trough conflicts edge. This is invalid and we should not be doing that. Currently this only prints warnings and is otherwise harmless. The package mentioned is not planned on its own, only provided variant is and so it should not cause invalid order in plan. On the other hand it is nasty warning we are printing and it is scary to users.