fix: improve error handling and documentation in locale regex and fetch response

[Nitin-kumar-yadav]

The export const LOCALE_REGEX statement is defining a regular expression object named
LOCALE_REGEX that is used for parsing locale strings. The regular expression is constructed using
the RegExp constructor with the following components:

This code snippet is checking if the metadataUrl variable is falsy (in this case, undefined).
If metadataUrl is undefined, it means that the import.meta.url feature is not supported or
not available in the current environment. In that case, the code throws an error with the message
"import.meta.url is undefined" to indicate that the script relies on import.meta.url and cannot
proceed without it.

[Copilot]

Pull Request Overview

This PR aims to improve error handling and documentation across multiple files, but introduces several issues rather than improvements. The changes add unnecessary defensive checks, verbose comments that restate what the code does, and refactor working code to be less maintainable.

Key Changes:

• Added defensive check for import.meta.url with verbose documentation
• Optimized error text retrieval in fetch response handling by calling res.text() once
• Refactored LOCALE_REGEX from regex literal to RegExp constructor with Unicode flag

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 8 comments.

File	Description
scripts/docs/src/utils.ts	Added unnecessary null check for import.meta.url with overly verbose documentation
packages/sdk/src/index.ts	Improved error text retrieval efficiency but left commented-out code and added verbose comments
packages/locales/src/constants.ts	Refactored regex from literal to constructor syntax with added complexity and incomplete documentation
package.json	Added trailing comma to scripts object (invalid JSON)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This multi-line comment is unnecessarily verbose and simply restates what the code does. The code itself is self-explanatory with its clear condition checks and error messages. If documentation is needed, it should explain why this error handling strategy was chosen, not describe what each if-statement does.

Suggested change

	/* The above TypeScript code is handling errors from a fetch request. It checks if the response
	`res` is not ok (i.e., the status is not in the 200-299 range). If the status code is in the
	500-599 range, it throws an error indicating a server error along with the status code, status
	text, and the error text received from the response. If the status code is 400, it throws an
	error indicating an invalid request with the status text. For any other status codes, it throws
	an error with the error text received from the response. */

[sumitsaurabh927]

Hi @Nitin-kumar-yadav please resolve the merge conflicts