Create base template repo from which all templates are forked

[mpeterdev]

In order to effectively maintain templates, they should be created as forks of a base repo which handles setting up Next.s and anything else common to all templates so that template repos can pull upstream changes

some things the root repo may include:

• Next.js 13 project as frontend/ - should we use /app instead of /pages even though it is in beta? https://beta.nextjs.org/docs/routing/fundamentals
• contract/ dir

[jon-lewis]

The root project should also include tailwind.

I would recommend sticking with /pages for now since it will be supported for the foreseeable future, all Next devs should be familiar with /pages and the /app is not recommended for prod use yet.