Added no-print flag

[poloaraujo]

resolves #4710

Description

Add a flag to suppress {{ print(msg) }} messages coming out of macros.

print functionality in macros was added in as part of #3451 but there is currently no way to keep the messages from being printed to stdout. This can result in these messages interspersed with logs going to stdout; macros using print() will always have the messages they are printing as an output.

16:31:35  Running with dbt=1.0.1
16:31:35  Found 5 models, 20 tests, 0 snapshots, 0 analyses, 180 macros, 1 operation, 3 seed files, 0 sources, 0 exposures, 0 metrics
16:31:35
16:31:40
16:31:40  Running 1 on-run-start hook
16:31:40  ********************This is a LOG line!
********************This is a PRINT line!

Describe alternative you've considered

Not doing this simply means that {{ print(msg) }} will always print to stdout.

Who will this benefit?

Right now, anything sent to stdout using {{ print(msg) }} will get printed to stdout all the time with no way to suppress it. This will allow anyone using macros utilizing print to suppress those messages.

Checklist

• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have added information about my change to be included in the CHANGELOG.

[emmyoop]

We've updated the process we use to generate changelogs so that you no longer have to manually figure out where they go. That's also what the cause of the failing GitHub action is. You'll need to delete this line and then go through the new process. You can see the details of how to do it in our Contributing guide.

[poloaraujo]

Thank you @emmyoop! I've updated the changelog following the new process and I've just pushed the changes.

[emmyoop]

Sorry this has been sitting for so long! It's looking great. Once you fix the changelog issue and the tests run successfully I'll take another look.

[sansar-choinyambuu]

@poloaraujo do you think you can do changes mentioned by @emmyoop regarding the CHANGELOG.md ? We need this PR merged ;)

[poloaraujo]

Hi @sansar-choinyambuu and @emmyoop! I'm sorry for the huge delay. I've updated the changelog following the new process and I've pushed it!

[emmyoop]

Looks good! I suggested just a small change to the changelog entry. The yaml file can be modified. No need to re-run the changie command!

[poloaraujo]

@emmyoop thanks! I've committed your suggestion.

[nathaniel-may]

LGTM