Adds script to backfill some of the CAP/CPA user events.

[wilkie]

This script will backfill the Cap::UserEvent table with records related to any folks that need it.

This is motivated by users being in the flow prior to the merging of specific recording of user events in our own database.

I could have built a View for this, but it felt easier to just backfill the few records in this window than maintain a database view that might have some issues when cloned to RedShift/Trevor.

Links

• jira ticket: P20-931

Deployment strategy

We would merge this and run the script on the production console. It does a 'dry run' where it writes out the records it would write. Then, you can commit that by running the script again. It should be idempotent.. if there are any failures, they will be found by running the script again.

There is a finite amount of old records since this is purely backfilling up to the date of the first actual user event record.

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked