DB migration

[insanity54]

• [x] fix thumbnail migration script so it doesn't depend on ipfs/ execa (use http requests only)
• [x] fix videoSrcB2 migration script
• [x] migrate on production strapi
• [x] rename api:patreon-benefit-id to api:patreon or whatever I changed it to
• [x] confirm patron login/logout works
• [x] confirm /profile save button works
• [x] deploy futureporn-uppy

[insanity54]

Today I learned that Strapi migrations are meant to run on both the dev environment as well as the production environment. I got that wrong and did a major roundabout way of backing up the production db, restoring it in dev, then running migrations in dev, then deleting the production db and finally restoring the migrated dev db to the production db.

For future reference, don't do that. Instead, implement robust migration scripts that depend only on portal HTTP requests. Then git push dokku main and let the migration scripts run in production.