Support populating DestinationTable in the response when using CREATE OR REPLACE table.name.foo AS (...) syntax

[andrewegel]

We're looking at using the bigquery emulator as a testing backend with the dbt-bigquery project - While investigating issue dbt-labs/dbt-bigquery#358 (comment) I found that this project doesn't populate the DestinationTable fields in the response to the client if the query uses the CREATE OR REPLACE table.name.foo AS (...) syntax. The emulator handles the case when DestinationTable is part of the Job Submit API call and a normal select * from source.table.foo (ie: bq --api ... query --destination_table 'table.name.foo' 'select * from source.table.foo), but dbt-bigquery likes to use the CREATE OR REPLACE table.name.foo AS (...) syntax because you can have more controls over how the results are materialized https://docs.getdbt.com/docs/build/materializations

I cannot speak to the feasibility of such a change, I'm just logging it as a behavior difference between BQ the service and the emulator.

[yaronneuman]

this is a duplicate of #180
there is also a merge request linked to this issue. I tried it myself and it works like a charm.