Fix next.config.ts using await in the top-level, breaking npm run dev in new projects

[nora-soderlund]

This PR removes the awaiting of setupDevPlatform and instead adds a catch to log to the console.

Currently, next-on-pages is broken for new projects, since you cannot run npm run dev because of this issue.

Fixes #927 and #925

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8e30649

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[beratbayram]

I am sorry if I am missing something but isn't it better to fix it like this:
#925 (comment)

[nora-soderlund]

// we only need to use the utility during development so we can check NODE_ENV
// (note: this check is recommended but completely optional)
if (process.env.NODE_ENV === 'development') {
	// `await`ing the call is not necessary but it helps making sure that the setup has succeeded.
	//  If you cannot use top level awaits you could use the following to avoid an unhandled rejection:
	//  `setupDevPlatform().catch(e => console.error(e));`
	await setupDevPlatform();
}

https://github.com/cloudflare/next-on-pages/blob/main/internal-packages/next-dev/README.md#example

potato potato. I don't really care how it is solved or what is the objectively better way.