chore(deps): update nextjs monorepo to v13 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-config-next	12.3.1 -> 13.0.0
eslint-config-next	^12.0.8 -> ^13.0.0
eslint-config-next	12.2.5 -> 13.0.0
next (source)	^12.3.0 -> ^13.0.0

---

Release Notes

vercel/next.js (eslint-config-next)

v13.0.0

Compare Source

vercel/next.js (next)

v13.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

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

Name	Status	Preview	Updated
inreach-app	❌ Failed (Inspect)		Oct 26, 2022 at 0:16AM (UTC)
inreach-web	❌ Failed (Inspect)		Oct 26, 2022 at 0:16AM (UTC)

[ghost]

👇 Click on the image for a new way to code review

• Make big changes easier — review code in small groups of related files

• Know where to start — see the whole change at a glance

• Take a code tour — explore the change with an interactive tour

• Make comments and review — all fully sync’ed with github

  Try it now!

Legend

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

installing v2 tool node v18.12.0
linking tool node v18.12.0
node: v18.12.0 /usr/local/bin/node
npm: 8.19.2  /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 7 seconds
skip cleanup, not a docker build: 8fd76d8374eb
installing v2 tool pnpm v7.14.0

added 1 package in 2s
linking tool pnpm v7.14.0
7.14.0
Installed v2 /usr/local/buildpack/tools/v2/pnpm.sh in 4 seconds
skip cleanup, not a docker build: 8fd76d8374eb
Scope: all 8 workspace projects
.                                        |  WARN  Ignoring broken lockfile at /mnt/renovate/gh/weareinreach/InReach: The lockfile at "/mnt/renovate/gh/weareinreach/InReach/pnpm-lock.yaml" is broken: duplicated mapping key (376:3)

 373 |     engines: {node: '>=6.9.0'}
 374 |     dev: true
 375 | 
 376 |   /@babel/compat-data/7.19.4:
---------^
 377 |     resolution: {integrity: sha51 ...
 378 |     engines: {node: '>=6.9.0'}
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 12, reused 0, downloaded 0, added 0
/mnt/renovate/gh/weareinreach/InReach/apps/app:
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing a direct dependency of /mnt/renovate/gh/weareinreach/InReach/apps/app

Your Node version is incompatible with "registry.npmjs.org/next-auth/4.15.0".

Expected version: ^12.19.0 || ^14.15.0 || ^16.13.0
Got: v18.12.0

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 13.x releases. However, if you upgrade to 13.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.