Fix CPAN Tester fails regarding using $^X instead of $Config{perlpath}.
Attempted fix of weird upgrade errors on some CPAN Testers reports.

The report lacks details on actual cause, but my best guess is the use of a
File::HomeDir default fetchware_package_path() on a smoker that may not have a
proper home directory. It might be a "server" style home dir instead of a proper
"user" style one Fetchware presumes.
Added FETCHWARE_DATABASE_PATH to another upgrade call.
Fixed exception string comparison due to $! localization.

Apparently people speak languages other than English. I obviously already knew
this, but failed to consider $!, and perhaps also $@ being localized to other
languages. This bug fixes one instance of this in this CPAN Testers report:

http://www.cpantesters.org/cpan/report/9132eae6-3568-11e4-aa59-cc92e0bfc7aa
Fixed redeclaring  twice in one subtest.
Updated t/bin-fetchware-command-line.t's test count to reflect new tests.
v1.013

    - Fixed dozens of CPAN Tester FAIL reports. These reports FAILed mostly
      beause they were run under a smoker, which is a different environment, then
      I test Fetchware under.
        - Fixed the upgrade tests actually using the users own fetchware package
          path. Now a temp file is used instead.
        - Switch use of $^X to $Config{perlpath}, which solves some bugs in some
          smoker configurations.
        - Fixed a hilarious bug due to localizations. I used a direct string
          comparison where $! was in the string, and I guess under different
          locales you can get languages other than english to come from using $!
          in a string.