Upgrade next and node-sass to the latest version

[tihuan]

Context:
We have a vuln related to node-sass: https://github.com/chanzuckerberg/single-cell-data-portal/pull/1248/files

Solution:

1. Upgrade next first at least to latest v12, since they have fixed their node-sass deps here
2. Now we should be able to upgrade node-sass!
3. next 11.1.3 upgrade alert: https://github.com/chanzuckerberg/single-cell-data-portal/security/dependabot/frontend/package-lock.json/next/open
4. chore(deps): bump next from 11.1.3 to 12.1.0 in /frontend #1980

[seve]

Just a heads-up, if this takes too many cycles. This trim-newlines vulnerability doesn't actually affect us. If the benefits of upgrading next aren't P0, I would recommend dropping the priority of this ticket.

cc: @maniarathi

[maniarathi]

@tihuan Do you think it makes sense to drop to P1 then given Seve's note?

[tihuan]

Thanks so much for the headsup, @seve !

@maniarathi : Yeah I think dropping to P1 sounds great, and we can just upgrade node-sass when we upgrade next in a few months once they port over Styled Components parser to SWC 🙆‍♂️

Github Issue: vercel/next.js#30802

Thanks both!

[maniarathi]

Can do this sometime in Q2 2022.

[tihuan]

Since next finally released 11.1.3, which is a patch version bump, I'll send out a PR to upgrade it after Perf! Thank you!

https://github.com/chanzuckerberg/single-cell-data-portal/security/dependabot/frontend/package-lock.json/next/open

[tihuan]

Turned out that Next only included the patch in v12:

vercel/next.js#34139 (comment)

[tihuan]

I think we've waited long enough for Next 12 to be stable, so maybe I can help upgrade to 12 this week? @maniarathi thank you!