React.js --> Next.js Refactor

[Vercin-G]

Once PR #57 becomes live, a fundamental rebuild of CavApps in Next.JS will be an eventual requirement.

This is due to the following reasons:

• As the JavaScript count increases, react will download every javascript file for every page in CavApps, even if certain pages are never opened by the end user.
• Severside rendering will allow us to eliminate the API call on the clientside. Thus removing the requirement to download an additional 10mb of data on the clientside.
• The CSS styling for CavApps is starting to become cluttered and intuitive. While manual styling may suit us for some time, Next.js' native support of external CSS tools may serve useful if others start developing in CavApps.
• CavApps was originally built as a single page ADR project. However, should we wish to expand to more serious development. i.e. utilizing authentication elements such as keycloak for multiple apps. It may be useful to update to a framework which allows us extra security.

[Vercin-G]

As of now, the code for the migration is complete enough to warrant a staging build and deployment. once i can iron out the staging build on a live setting, i can finish off work on the migration.

see here for the current nextJS version: https://github.com/Vercin-G/adr/tree/nextjs-dev

[SyniRon]

closing as this was done in #70