Fixed t/bin-fetchware-util.t bug where a test was too specific to my computer.

I used an eq test instead of a like test, which messed up the test, because I
tested for a specific value that only exists on my computer, and will obviously
differ on other computers.

This is also the first in a series of commits to fix bugs discovered by the
awesome CPAN Testers folks! Thanks for the test report!
Fixed optional Test::Expect bug in t/bin-fetchware-new.t

Test::Expect is "optional" for testing. That means that only if its "already"
installed will it be used. Perl does have a cool TestRequires mechanism, but
expect is wonky on Windows, and I don't want to worry about that, so I only want
to use Test::Expect if it's already installed. I do not want it installed for
testing like the whole TestRequires thing does.

Fix for test report:
http://www.cpantesters.org/cpan/report/48b619bc-5235-11e3-88f0-885982088f79
Fixed POD error in Test::Fetchware.
Fixed hash order randomization bug in t/App-Fetchware-Config.t

More annoying hash algorithmic complexity attacks were found in Perl's hash
implementation again, causing randomization to always be on making unknown hash
order dependency bugs more obvious. One such bug was found in
t/App-Fetchware-Config.t. I almost fixed by using a subroutine instead of the
simple heredoc, but that fix used evil eval. Instead, I fixed it with cleverness
by simply only storing one value in the hash I no longer depend on the order,
because it's always the same, because there is only one value to order, which
obviously only has one order.

Fix from Tester report:
http://www.cpantesters.org/cpan/report/48b619bc-5235-11e3-88f0-885982088f79
Fixed "masks earlier declaration" bug in t/bin-fetchware-upgrade.t.

The copy and paste coding style I always seem to fall into when creating
Test::More style test suites caused 2 variables to have the same name. Renamed
the second one. Problem solved.

I've considered creating some sort of macro system for creating easily
repeatable testing code similar to copy and pasting, but without the actually
coping and pasting. But would such a system be stuck using a source filter :( ?
Or use subroutines that are called with args, and create a fancy easy to use
function factory to make them all??? Would it even be worth it. A macro system
would also fail the grep test, which isn't always such a big deal.

Fix from test report:
http://www.cpantesters.org/cpan/report/48b619bc-5235-11e3-88f0-885982088f79