Bug: Overly verbose info-level logging for BigQuery queries that 404

[drewbanin]

Describe the bug

I noticed this while reviewing #2378 -- when the catalog query failed with a 404 error, I saw the entire contents of the catalog query printed to stdout. Instead, the verbose BQ-generated error message should be logged to the debug logs.

Steps To Reproduce

This happens for both dbt run and dbt docs generate, and probably others too

1. Set your location to US in your BQ profile
2. Do a dbt run that creates at least one model in the db
3. Change your location to northamerica-northeast1
4. Run dbt run again and observe the stdout

Expected behavior

Stdout should not include the entire contents of the query that failed

The output of dbt --version:

dev/octavius-catto