Fix Next.js type references in Next.js >= 13.2.0

[valentinpalkovic]

Closes N/A

What I did

Added some type references for Next.js stories, since they are necessary since Next.js 13.2.0, because some types in next/navigation are not exported per default, but type references are dynamically created during Next.js start up instead. See vercel/next.js@cdf1d52 for more insights.

How to test

1. Run a Next.js sandbox: yarn task --task sandbox --template nextjs/default-ts
2. Go to your sandbox directory
3. Open next.config.js and add { experimental: { appDir: true }} to the configuration
4. Add a empty app folder in the sandbox
5. Start Next.js once (yarn dev) and abort it after it started successfully
6. A next-env.d.ts should be created with these entries:

/// <reference types="next" />
/// <reference types="next/image-types/global" />
/// <reference types="next/navigation-types/compat/navigation" />

// NOTE: This file should not be edited
// see https://nextjs.org/docs/basic-features/typescript for more information.

7. Open stories/frameworks/nextjs_default-ts/Navigation.stories.tsx -> The import shouldn't error.

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[yannbf]

LGTM!