Bug: fixup bq _partitions_match for range partitions

[jtcohen6]

Fixup to #2140

The issue is just a matter of matching the structure of the object in the BQ API.

Steps to replicate

Running with dbt 0.16.0, create a model that is partitioned by an integer range. Change the partitioning spec and run --full-refresh.

First error:

AttributeError: 'Table' object has no attribute 'range_partition'


It's called range_partitioning

Second error:

AttributeError: 'PartitionRange' object has no attribute 'field'

The field key is nested under range_partitioning, rather than under range_partitioning.range_

[beckjake]

The fix looks great, but can you add an integration test that exercises this path so we don't regress? I'm happy to help with that - I can't remember if you've written dbt integration tests before.

[jtcohen6]

Surely. I added a test to TestChangingPartitions, which seemed most relevant.

[beckjake]

Looks great, thanks for the test! - I've verified that the test correctly fails without this fix, so hopefully no more regressions.