chore: adding new migrations (and s3 copy helper function)

[ealexa05]

This starts our convoluted recovery scheme for Masabi data with minimal disruption for analysts:

• run this migration, to copy 1-year data over to a new MASABI_TEMP location in case the new fix doesn't work as intended
• apply the fix in Fix masabi parquet rollover error #175
• wait to verify behavior
• run another move migration to copy completed 1-year data over to copy over to MASABI_TEMP
• put in the schema change PR (Add masabi temporary schema #176; beta instance will be saturated, but duck_db.py will run at some point because it is running on alpha)
• Put in a new delete migration to delete 1-year data in MASABI_DATA and kick off ingestion of 5 year data