docs(nextjs): use custom build path rather than output path

[kirjai]

Current Behavior

This contains two fixes:

• Currently, the two Vercel deployment images are broken:

• also, we currently encourage people to use the --outputPath=. option when deploying to Vercel, however that is no longer the preferred approach. In fact, using --outputPath=. is causing issues with latest versions of Nx. (--outputPath=. causes error without helpful message #5982, Command to build Next.js for Vercel errors out #5748, Deploying next.js app to vercel or netlify throws error #5660)

Expected Behavior

• the docs should not encourage using --outputPath=.
  • changed the docs and screenshots to reflect that a custom build output path should be used instead
  • done so only for the "latest" version of the docs though
• images should work
  • so what i've done is moved those images from a github link to the repo (i did optimize them manually with tinypng).

Related Issue(s)

Fixes #5982, #5748, #5660

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/A5hN686Qseu9ocZu4WGDYUUxrMpm
✅ Preview: https://nx-dev-git-fork-kirjai-next-docs-dist-path-nrwl.vercel.app

[kirjai]

having this unused import here has been throwing an error on CI. not entirely sure why this isn't an issue on master even though this branch is rebased and up to date at the time of writing.

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 49842a2. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx affected --target=build --parallel --max-parallel=3
	nx affected --target=e2e
	nx affected --target=lint --parallel --max-parallel=4
	nx affected --target=test --parallel --max-parallel=2
	nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.