No schemas; merged tables; platform labels

[berekuk]

Lots of changes!

• 25

• merged history tables in a single table and merged platforms tables into public.questions table; "merge" job is no more necessary
• wrote a custom migration script for this (src/backend/manual/noSchemaMigrate.ts)
• fixed #41
• all internal code uses short platform name (goodjudgment instead of Good Judgment), labels are used on frontend only (and also pushed to algolia to the new platformLabel field for easier frontend logic and maybe search)
• moved labels and colors to platforms code, so data for each platform is colocated in a single file now
  • it's passed to frontend from getServerSideProps

• 13 is also fixed, btw

• remove legacy fuse-related code

Don't deploy this yet! There are a few manual steps I'll have to do first to avoid downtimes, and also there are so many changes that I'd like to recheck everything first, it's quite possible I broke something. And some small bits (e.g. secretEmbed) are currently broken, will fix before deployment too.

Planning to do this tonight or maybe tomorrow, depending on how many issues will show up on the final check.

[netlify[bot]]

✅ Deploy Preview for metaforecast ready!

Name	Link
🔨 Latest commit	1b6ff8d440cc99c34ff5dbc71851e259e8299460
🔍 Latest deploy log	https://app.netlify.com/sites/metaforecast/deploys/624789e0cbcf9800088d1a4d
😎 Deploy Preview	https://deploy-preview-42--metaforecast.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[berekuk]

I left this comment in a merge commit, meant to post here. Copying.

Should be fine. Tables in public schema are ready.

Fixed secretEmbed and dashboards, fixed small bugs in platforms code (I'm starting to dislike the fact that platform fetchers have to populate platform field and set id to ${platform}-${shortId}, it seems error-prone; maybe platforms should remove an object with id: shortId and without platform, and then an external code would populate it as needed... but then we'd need a different type for "fetcher output result", and I'm still hesitant).

Steps for the next half-hour:

• [x] move tables to new DB instance in the US (copied with pg_dump/pg_restore)
• [x] merge code, deploy on heroku/netlify
• [x] switch to the new db
• [x] update algolia index
• [x] check that everything works
• [x] drop schemas (from new DB, not a problem even in case of significant issues since we have backups and the old DB)