This is actually NOT how conflicts work in metadata

The purpose of this plugin is to warn the user that updates should be made
*after* installing the dist, *not* that the specified module cannot be present
during the specified phase
CPAN::Meta::Check up to and including 0.005 has a code error in conflicts checking

..which is fixed in https://github.com/Leont/cpan-meta-check/pull/4
add two more dzil plugins that do not like seeing range operators in prereq data
and Test::CheckDeps 0.006 fails (without TODO) when conflict metadata checks fail