CHIRP

In order to support a CLI (see issue #2343), the level of output needs to be variable, from terse to verbose. The proper solution will be to use the standard Python logging module. All existing print statements need to be reviewed, as most will need to be converted to use a logging call.

I have patches in hand that get this process started. The first adds a custom logger module and command line options for controlling it from the chirp.py CLI. The second adds all existing debug statements (controlled via CHIRP_DEBUG) to use it. The last converts a handful of other message to use it as well, making the CLI usable.

Additional patches will be required to convert other print statements and to add equivalent option parsing to the GUI.