Feature/add eslint and cleanup deps

[he-james]

Still doesn't do much for cleanliness and best practices. That will be achieved in my next PR.

Reviewers, please be mindful that I literally died to make this. I am now a corpse. If it can be fixed in less than 10 minutes, I will do it, otherwise, I am making the executive decision that each review comment is a "Should" instead of a "Must". I'll be glad to make the changes needed after this is merged in my next branch, as to go this long with out this branch going up is to cause pain to my brain.

Most notable changes:

• Literally all the syntax
• Project structure vaguely reflects conventions either I have seen or I have read about in this process. I think most similar to https://wityan.medium.com/next-js-project-structure-1531610bed71
• Storybook was removed. - @FB-Reda, this was your suggestion, and I actually quite like Storybook - the reason for its addition to the gitignore for now is so that I can take the time needed to standardize it.
• NextJS was upgraded to Next 12
• _document.tsx includes font links per NextJS docs on font optimization
• For now, if this causes trouble with y'all's local dev workflow, either (1) do something locally, (2) checkout an older commit, or (3) do nothing and deal with it for the time being.
• Usage of compilerOptions.baseUrl and compilerOptions.paths in the tsconfig.json - this is a very essential add, since it cleans up imports rather substantially. Maintainers are welcome to add paths whenever convenient and reasonable.
• Addition of .husky/ directory and husky pre-commit lint-check - This fixes lint wherever it can, and prevents commits that require manual de-linting. You may find this annoying, but I find lint annoying.
• A somewhat strict refactor of js -> ts/tsx file extension changes and their code. While using typescript is not required still, I've did this refactor in the middle of the night while I was trying to figure out many type-related errors. I am fairly certain it is still possible to write untyped JS in this repo, but I will say that it will be somewhat more difficult. That being said, feel free to give development a shot - there will be some initial learning curve and frustration, but the benefit of fairly decent typing is that most IDEs will support retrieval of type documentation. This means that writing out props and other type/class attributes has never been more convenient.

Anyway, feel free to explore. I'd recommend checking this out in your own environments and giving it a look-see. This is a pure refactor to add ESLint to our repo and passed the pre-commit check, but obviously cosmetic and readability improvements are highly encouraged.

[vercel]

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

🔍 Inspect: https://vercel.com/model-un/cimun-web/9zNdBGpapWpwDhSLqEUsttbvhVub
✅ Preview: https://cimun-web-git-feature-add-eslint-and-cleanup-deps-model-un.vercel.app

[FB-Reda]

Is there anything we still want out of this? I think we're maybe taking a new approach to cleanup and updating so some of it may be less relevant. Additionally merge conflicts on this might be quite difficult.

[FB-Reda]

Outdated