Payments: Dedupe rows on all incoming tables

[lauriemerrell]

We currently dedupe Payments micropayments data to account for the fact that the same data can be uploaded multiple times (and because we sometimes get multiple full duplicate rows). We should add the same handling on all Payments tables. ( ⚠️ Primary key to use for deduplication will vary; we should aim to dedupe down to the entry/file level in staging tables, I think.)

• LP authorisations
• LP customer funding sources
• LP device transaction purchases
• LP device transactions
• LP micropayment adjustments
• LP micropayment device transactions
• LP product data
• LP refunds
• LP settlements
• Elavon transactions (double check whether applicable to Elavon data)

[lauriemerrell]

Transferring from offline conversation: We have discovered that the current micropayments QUALIFY probably deserves a bit more scrutiny. We are finding a fairly large number of cases where it combines rows with distinct transaction_time values, whose interpretation is unclear to us.

[lauriemerrell]

This is closed in #2993 and #2994