[Feat] - Dev Portal v2

[gowthamsundaresan]

🚨 Notice 🚨

Before deployment:

• All EE clients must switch their existing EE_AUTH_TOKEN to a newly generated API Token w/ access level set to 999
• Make sure the following env vars are set

SUPABASE_PROJECT_REF
SUPABASE_EF_SELECTORS

After deployment:

• The following env vars can be safely deleted

SUPABASE_FETCH_ALL_USERS_URL
SUPABASE_FETCH_ACCESS_LEVEL_URL
SUPABASE_POST_REQUESTS_URL
EE_AUTH_TOKEN

Updates

• Custom route pricing. In v3, we would implement this by adding routeCost(n) to route definition like this:

router.get('/:address', routeCost(2), routeCache.cacheSeconds(120), getAVS) 

Note: Placing routeCost() after routeCache.cacheSeconds() would cause cached responses to cost the default amount of 1 unit

• EE_AUTH_TOKEN deprecated. EE clients are to use their own individual API Tokens w/ access level 999.
• Consolidation of multiple edge function env vars to a single multi-selector
• Auth store is now updated after every update posted to the dev-portal. Hence we have moved completely from push to pull.
• Auth store lifetime reduced to 1-hr, after which it updates mandatorily with the next req
• Optional exclusion of auth. API Token requirement and comms w/ dev-portal DB can be turned off if any one of SUPABASE_SERVICE_ROLE_KEY, SUPABASE_PROJECT_REF, SUPABASE_EF_SELECTORS are not set