Update to Next 14!

[advaithg]

Resolve #400

Refer to Next 12's release notes here

A huge breaking change to deal with is that merging this in will result in the surrounding element for next/image being a <span> instead of a <div>, making them inline by default, so that will have to be fixed for all uses of <Image> in our codebase that are impacted (see this deploy preview's carousel for an example of something breaking)

[mattxwang]

This is not related to #406 - that changelog has nothing to do with Next 12.

This does affect lint, etc., other packages that need to be updated in lockstep with Next 12.

Also keep in mind the previous problem I encountered - deploying Next 12 on Netlify without using Netlify functions, since that's not within our budget.

[matthewcn56]

Also keep in mind the previous problem I encountered - deploying Next 12 on Netlify without using Netlify functions, since that's not within our budget.

I think Netlify functions are within our budget, we just have to be wary of how many times they can possibly get triggered and make sure that we don't go over the 100k invocation limit every month.