[BE] Deprecate current hypercerts supabase instance in favor of hypercerts-staging

[Jipperism]

What is it?

Once the revamped frontend is online, we should deprecate our current supabase instance. Reason for doing so is it's not migration-based so a liability. It also carries a lot of technical debt.

Steps:

• Double check with all team members which tables are relevant, and which can be thrown away (see also discord discussion
• Move over table structure, into migrations for hypercerts staging
• Move over data
• Run a modified version of the claim id update script (scripts/update-claimids-in-supabase-to-multichain.sql)
• Update defender tasks:

  
  // defender/src/auto-tasks/batch-mint-claims-from-allowlists.ts
  const formattedClaimIds = claimIds.map(
  (claimId) =>
    `${network.chainId}-${contractAddress}-${claimId
      .toString()
      .toLowerCase()}`,

// defender/src/auto-tasks/mint-claim-from-allowlist.ts const formattedClaimId = `${network.chainId}-${contractAddress}-${claimId

// defender/src/auto-tasks/on-allowlist-created.ts claimId: ${network.chainId}-${contractAddress}-${tokenId},

- Update supabase instance in marketplace sdk
- Update supabase instance in hyperboards
- Update supabase instance in starter apps

[bitbeckers]

New supabase-staging setup for reference: https://github.com/hypercerts-org/hypercerts-indexer/tree/develop/supabase