fix: fixed localized links and next links redirection

[ovflowd]

Description

This PR is a "hot-fix" PR that does the following changes:

• It updates the LocalizedLink component by conditionally either rendering next/link or a href
• We removed some usages of LocalizedLink when it's not needed
• Remove the Vercel Analytics from Static Exported builds
• Refactoring LocalizedLink by adopting memoization

There are minor unrelated changes (such as removing an eslint rule that is unnecessary) and npm run format reformatted an SCSS file.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 5, 2023 4:18pm
nodejs-org-stories	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 5, 2023 4:18pm

[ovflowd]

Requesting fast-tracking @nodejs/build @nodejs/website

[richardlau]

Looks like Prettier is complaining https://github.com/nodejs/nodejs.org/actions/runs/5466287396/jobs/9950981528?pr=5474#step:7:20

[ovflowd]

This PR is a result of some of the studies done over This Slack thread that is part of the long-term investigation regarding the website stability on the DigitalOcean infrastructure, which is occasionally causing flakiness on our infrastructure.

As explained previously (including on the March 17th incident post-mortem), CloudFlare does not cache 404 requests, and some requests originated by Next.js itself (Next.js pre-fetching URLs) were causing high-load on our DigitalOcean infrastructure.

This PR removes the unnecessary pre-fetching from external links not hosted by this repository/the Next.js framework we use here, effectively reducing the amount of 404s.

This might alleviate some of the pain on the DO's servers. Remember that regardless of the current "incident", external links should not be pre-fetched by Next.js.