Add utils for logging to the command line

[clrcrl]

I thought about how to test this, but it gets pretty hard given the output depends on the clock time. I wanted to do a regex match on the output, but Jinja doesn't support this.

In the end, I thought it would just be easiest to test if the output is a string 🙂

[drewbanin]

Cool PR @clrcrl! How would you feel about adding a log_info macro that just goes ahead and invokes:

{{ log(dbt_utils.pretty_output_msg(<the message>), info=True) }}

It seems like this is the intended use-case anyway, right?

[drewbanin]

When I saw this PR, I imagined the output would instead look like:

11:07:31 + my pretty message

What's the motivation behind placing the timestamp on the right side of the divider?

[clrcrl]

Ah, so I was largely following the pattern from here (and in fact means to swap that code out).

I like having it indented as it makes it clear that it's being called from within a model (to me at least). But happy to change it if you feel it's unintuitive.

[drewbanin]

yeah, I'd go ahead and swap it around I think unless you feel strongly that it should work the way you've already implemented

[clrcrl]

Yah can for sure add a log_info macro – I back-and-forth-ed as to whether I should actually call the log function or not, so very happy to do that :)

Is the naming okay? I took inspiration from pretty print, but am also happy to rename it.

[drewbanin]

I'd maybe just consider changing pretty_output_msg to pretty_log_format or similar, but otherwise I'm happy with these pretty names :)

[drewbanin]

LGTM