Allow caller to control driver logging

[astrieanna]

CLIs that use cnab-go should be able to:

1. Control whether any output is written
2. Control whether output is written to stdout or stderr
3. Capture all output (i.e. to store logs for future reference)
4. Get logs from all the code in the driver (i.e. SetConfig should be able to write logs, too)
5. Separate logs from the invocation image from logs from the driver (very important for UX)
6. Control verbosity of the driver logging

This is related to:

• The existing issue about the Docker driver writing directly to stdout (https://github.com/deislabs/cnab-go/issues/78)
• A discussion when adding more-than-usual user feedback to the Docker driver's SetConfig (https://github.com/deislabs/cnab-go/pull/139#discussion_r331246080)

Currently, the caller can set stdout and stderr streams in the Operation, which allows the caller to control whether output is written, whether it's written to stdout/stderr, and to capture the output. It does not allow logging from SetConfig. There are not enough tests to ensure that the logging is consistently done only to the Operation streams.

Some possible approaches:

• Use the same logging library in both the caller and cnab-go; for libraries with shared global settings, this would allow the caller to control the verbosity and make the logging more reliable (using a logging library is more obvious than digging up a stream from an object to write to), but doesn't distinguish container vs driver logs or necessarily allow the caller to capture all output.
• Construct each driver with a logging object (streams or whatever); this could be similar to how logging works for the main function today, but the object with the streams needs to be introduced earlier, so that SetConfg can use it too. Because this would be a custom-for-drivers object, we could include separate streams for before the container runs, the output of the container, and after the container runs (to support the most basic form of interleaving logs when showing them to the user).

cc @youreddy @silvin-lubecki

[carolynvs]

I recently fixed the docker driver in #234. It would be great to be able to separate out driver logs and the output of the bundle as well though. 👍