Test cases for masking passwords in output & build logs.

There is a test case for each backend: LWP, wget, curl.
Add function to mask passwords.

I chose to use "*password*" as the mask because that is what
wget uses (or curl, I forget which).

When using wget or curl for the backend, they will emit their
own stuff to STDIN or STDOUT.  We can't easily sanitize that,
but I trust that they will not leak the password either.
Mask URIs on output methods

When we are printing a URI, the original method call is now wrapped
with a masking function so we don't put URI passwords into the log
or screen output.
Merge pull request #281 from dagolden/topic/mask-uri-passwords

Mask URI passwords in output (alternate approach)