App::DuckPAN: move verbose option to App level.

There's no particular reason why verbosity should be set on only the
server command level.  If we move it here, we can better unify logging
and create a more consistent interface.

This is a breaking change for scripts which expect the other ordering,
but it will really improve things.  So let's do it now, early in
product up-take.
App::DuckPAN: add and use verbose message.

We abviously aren't _overly_ concerned about speed, so the early return
guard there is mostly in case we decide we want to mutate the output or
something else fancy inside `verbose_msg`
DuckPAN: switch print_text to show_msg.

This creates a more consistent API and is easier to think about in a
general way.

`exit_with_msg` stays as it is, because an extra argument is required
which should be slightly more obvious with the naming difference.
Replace print with show_msg.

We want a consistent way of outputting messages, so all of the print
statements with access to the App are converted to use its outputters.
App::DuckPAN: add warning_msg and error_msg.

Still more abstracting of the output such that we can potentially do
interesting things with it later

Also:
- Move meat of show_msg into _print_msg with filehandle passing.
- Put error_msg on to STDERR via the above facility.
- Minorly refactor _print_msg for slightly tighter output and better
  comprehensibility.
DDG: turn per-class loads into verbose messages.

It all scrolls by so quickly that it is unlikey to help.  It's mostly
the unable to load messages which are of interest. Those also become
warnings herein.
Direct Data::Printer output to msg mechanisms.

This way the info gets caputred in the same ways.
DuckPAN: drop line splitting.

It's a lot of wasted cycles in 2014 to do this kind of thing.  If
someone cares, they probably have a terminal setting to do it.  If they
don't, the cycles are even more wasted.

Includes some message review work as well, in an attempt to make sure
this isn't insane.
DuckPAN: prepend log level on each line.

With the word splitter gone we can better format these messages such
that if they span several lines, they look "blocky" enough to logically
group.
DuckPAN: update some message outputs.

Having run this, I saw some places where the messages are less
appealing, now that each line ends.  This is fixing up some of that.
Covert DOS to UNIX line-endings.

I have enough trouble with the mixed tabs and spaces; I don't need this
hassle, too.
DuckPAN: improve exit_with_msg for good and bad exits.

There's no point in yapping about a FATAL ERROR when the exit is 0.
Also, if it IS an error send it to STDERR.
DuckPAN: improve switch documentation
DuckPAN: use _print_msg internally.

This fixes a bug with exit_with_msg.. as well as preparing for the
future goodness.

Also, a mis-aligned exit code for the unknown command path.
DuckPAN: add colored prefixes.

This isn't too distracting, but maybe adds some value.  Also, not
expected to be the final version.
DuckPAN: rearrange outputting, again.

- Organize into 'emit_<msg_type>'
- Prefix pretty much everything.
- Add fixed-width prefix-maker
remove colour and prefix from standard and verbose output
DuckPAN: move prefix-appending into `_print_msg`

This may (or may not) make it easier to do more interesting things with
the various kinds of output.
Server: left-align ProgressBar.

Already seeing the problems with something which doesn't go through the
`emit` process.  It's still helpful, but it requires extra maintenance
effort when the assumptions change.
DuckPAN: bold all prefix lines, NOTE -> NOTICE

The intention is to have them stand out a bit, so this should help.
In the old case, it could blend in with the output if the user happens
to be using a chosen color as their base color, since there aren't
any obvious prefixes on the standard output. If people run with bold all
the time, they deserve what they get.

I dunno why I like NOTICE better, but I somehow do. This means expanding
the prefix_width.. which might be moot now that we don't always prefix.