tweak to getting started instructions
make tests more robust

* detect if correct version of Test::More is installed
* clean up warnings
allow for bin itself to be recursive
deprecate implied recursion

Up until now, recursing into a subdirectory could be specified by just
putting the name of the directory in .dfminstall, like this:

-----------------
.ssh                 <--- causes dfm to recurse into the .ssh dir
README.md skip
t skip
-----------------

This is slighly confusing, because to just skip a file, a 'skip' keyword
was required.  This change makes recursion behave the same as skipping.
The above file should now look like this:

-----------------
.ssh recurse         <--- causes dfm to recurse into the .ssh dir
README.md skip
t skip
-----------------

A deprecation warning will be displayed if implied recursion is used.
handle switching to recursion
fix bin recurse test
Replaced relative paths with absolute paths in the install_files recursion code to fix mkdir mishaps

The tests for links and directories in install_files recursion code were relative paths so
when more than one directory was specified for recursion in a .dfminstall file the tests
would be run for the wrong locations.

This fix uses absolute paths which ensures the locations are correct.

This fix also adds the absolute paths to debug output for the recursion code in both
install_files and uninstall_files for clarity when debugging.
update tests to work with latest git
testing parallel recursions
set fetch_updates to use the appropriate upstream

not hardcoded to origin anymore
removed all hardcoded origin refs
first test for non-origin remote
Merge remote-tracking branch 'nsp/master' into non_origin_remote
more robust way of finding upstream (@{u})
perltidy
oops, forgot to rename function
perltidy
add helper for focusing on a particular subtest

and call the function in each subtest
allow using .bashrc instead of .bashrc.load

Fixes #9
added option to execute files from .dfminstall