[Feature] [Architecture] Migrate to NextJS for Dynamic On-Demand Page Generation

[elchris]

so it looks like NextJS does indeed support React true server-side rendering, unlike Gatsby:

https://nextjs.org/learn/basics/create-nextjs-app
https://nextjs.org/docs/basic-features/pages#server-side-rendering
https://nextjs.org/docs/basic-features/data-fetching#getserversideprops-server-side-rendering

• they definitely try to nudge you toward deploying to their platform https://vercel.com/pricing
• however we can deploy it to our own server https://nextjs.org/learn/basics/deploying-nextjs-app/other-hosting-options

but deploying to their platform gets you a more straightforward deployment pipeline, which I'd otherwise need to replicate on AWS hosting which is .... doable ... and which i could also roll out for the API application itself.

i'm thinking we should replace gatsby + netlify with nextjs + vercel , maybe if we can cut a deal with them or something.

@ThugDebugger also just mentioned to me that Netlify also has native support for NextJS with a small incremental cost to allow server-side rendering, so that might work too?

This should give us all the things we care about:

• do dynamically-rendered pages on-the-fly for business profile pages, and i would also recommend generating the paginated listing pages server-side as well, because that'll be the most reliable way for google to discover, index and rank them. Those dynamic pages can get their data in real-time from the API, and stream out html to the end-user/search engines --- no more "static site generation" headaches.

• for things that are dynamic but do not require search engine visibility such as "Developer Portal" and "Owner Portal", we can stick to the simpler model of static single-page React App w/ client-side API interactions authenticated by OpenID Connect