fix package name for these cookbook documents
remove package statements from .pod, but preserve "provides" metadata and recipe munging

perl -p -i -e's/\A/# Dist::Zilla: +PodWeaver\n/m; s/use (strict|warnings);\n//mg; s/package /# PODNAME: /m; s/# ABSTRACT: //m; s/;\n/ - /m; BEGIN { undef $/ }' $(find lib -name \*pod)
remove unneeded lib includes
Fix x_breaks entries, and generate the test that checks them

Conveniently this also fixes this issue:

<@haarg> ether: for the zzz-moose-outdated test, i get a lot of failures like 'MooseX::App is version unknown, but must be greater than version 1.22'
<@haarg> because they are trying to load Moose from blib, but it doesn't have a VERSION
<@haarg> this is using the Makefile.PL, not dzil
<@haarg> not a huge issue, but it might be worth defining a $Moose::VERSION and $Class::MOP::VERSION in that test
< ether> hmm yeah, that test wouldn't work so well from the repo when using the placeholder Makefile.PL
< ether> it doesn't make much sense to run the test at that point; it can just be skipped
 * ether flags this for fixing tonight.
< ether> actually I don't think the placeholder Makefile.PL is working out so well right now in other places, too...
< ether> anything that uses a dependency that then does a Moose->VERSION check will also suffer the same fate
< ether> I recall upasana running into this with MooseX::WithOverloading code a while back
< ether> so yeah maybe we should just hack $VERSION to 9999
< ether> ..or something
<@haarg> it generally doesn't matter, since the tests shouldn't be loading things that depend on Moose
<@haarg> it was a problem when depending on MooseX::WithOverloading, but that only would have worked as a proof of concept anyway
<@haarg> so i think hacking the version of Moose and Class::MOP (maybe Moose::Role?) to 9999 for that one test might be reasonable
<@haarg> or just having it skip when run via the placeholder makefile
< ether> I'll play with both variants. skipping might be better since Moose::Conflicts is generated via dzil anyway, so we'd be running the one that's actually installed, or blow up if there is no version installed yet
bump version to 2.1205