Bug: Incorrectly named Littlepay columns prevent data movement

[SorenSpicknall]

Describe the bug
Due to mislabeled column names in our external table creation process (stemming from copy/pastes from an old Littlepay-provided data dictionary that itself had some errors), a couple of our Littlepay tables include columns that are erroneously empty. The ones I've identified are as follows:

micropayment_adjustments - zone_ids_us should be zone_ids_used
device_transactions - transction_deny_reason should be transaction_deny_reason
product_data - capping_overlap should be capping_overlap_time

To Reproduce
Check these column names in the external table creation YAML files and downstream models against the titles of those columns in raw copied source files in GCS.

Expected behavior
Once these column names are corrected, source data should flow in correctly for these columns.

Additional context
A full fix will require us to reprocess old Littlepay source files into their parsed form