Fix page reloading bug by switching to local implementation

[JeremyKennedy]

By making 100% of the app logic local, this simplifies many things:

• infrastructure: now there is only static content to deploy, no need to worry about an API or serverless functions or cold starts
• frontend behavior: instead of having to make a network request and wait for a response, the frontend is now able to instantly process data, meaning the app processing is super fast, and needs no internet connection (once loaded)
• deployment: there's no fancy "static site generation" or "server site properties" or whatever fancy web magic Next.JS offers, just a simple static site

Initially we went with the backend API approach for app logic as we were considering databases, authentication, and whatnot, but that is all out of scope. Adobe Analytics is implemented and is all we need.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

eligibility-estimator – ./

🔍 Inspect: https://vercel.com/eligibility-estimator/eligibility-estimator/8gxn1YPQA5d77hRFLZsh6rGGxwHa
✅ Preview: https://eligibility-estimator-git-feature-3506f2-eligibility-estimator.vercel.app

[KhalidAdan]

I'm okay with this, but just left a thought that we could chat about at any time really. The solution came out clean!