Improve next.config.js readability and robustness with clearer path resolution and comments

[NirajDN]

Why:

Improved next.config.js for better readability, maintainability, and adherence to best practices.

• Used nullish coalescing operator for safer environment variable fallback.
• Simplified async rewrites function syntax.
• Added meaningful comments to clarify configuration choices.
• Ensured webpack config excludes server-only modules like fs from client bundles.

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

• Refactored and cleaned up next.config.js file.
• Improved inline comments for clarity.
• Example update from rewrites function:

async rewrites() {
  return productIds.map((productId) => ({
    source: `/${productId}/:path*`,
    destination: `/${DEFAULT_VERSION}/${productId}/:path*`,
  }))
}

[Copilot]

Copilot wasn't able to review any files in this pull request.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

[Ekene1998]

next.config.js