Deploy a new Amplify app for V2 of the website

[what-name]

The currently deployed app has an unkown problem that doesn't let it be pulled and edited. Because of this, that App's backend environment can not be updated or edited anymore. Any Amplify app's backend environment can be pulled with amplify pull --appId myAppId --envName dev. This downloads and sets up the project (the amplify folder only) for local development in a guided way. When doing this with the currently deployed app, it returns an obscure no such key error. I have not been able to find the source of this problem, but I am 99% sure that it's isolated to that specific deployed app as it persists between development environments and @rishabkumar7 has the exact same issue on his machine as well. I have deployed multiple Amplify Apps on multiple accounts and all of them can be pulled no problem.
My proposed solution is to create the V2 of the website, deploy it as a brand new Amplify app and switch the domain over.

I'm working out the details on my proposed deployment strategy that would stay clean down the road as well (environment names, staging etc). Will update this issue soon.

[what-name]

Consolidated & moved to #12