Update check-is-release.ts

[Pterjudin]

The refactor improves readability and maintainability by extracting process.cwd() and the package JSON path into constants to reduce repetition. Error handling is enhanced with a more descriptive error message, providing better context for debugging. The redundant if/else logic for writing "true" or "false" to Bun.stdout is streamlined into a ternary operator for conciseness. Optional chaining is introduced to safely access releasePlan.releases, preventing potential runtime errors if the object structure is undefined. Finally, a JSDoc comment is added to clearly document the function's purpose and behavior, making the code more understandable for future contributors.

Description

The refactor improves the checkIsRelease function by enhancing readability, maintainability, and reliability. Repeated logic such as process.cwd() and the package JSON path are extracted into constants to minimize redundancy. Error handling has been improved by adding a descriptive error message for better debugging context. The conditional logic for writing "true" or "false" to Bun.stdout has been streamlined into a concise ternary operator. Optional chaining is used to safely access releasePlan.releases, avoiding potential runtime errors due to undefined object structures. Finally, a JSDoc comment is added to document the function's purpose and expected behavior, aiding future contributors in understanding its role and output.

Related Issue

This PR does not address a specific issue but improves the code's overall quality and robustness.

Motivation and Context

The changes improve the code's maintainability and readability, making it easier for contributors to understand and extend. It also reduces the risk of runtime errors by handling undefined structures more gracefully and enhances developer experience by providing better error context and streamlined logic.

How Has This Been Tested?

The refactored function was tested by running it in multiple scenarios:

1. With a valid releasePlan containing expected releases to ensure the output is correct.
2. With missing or malformed releasePlan data to verify robust error handling.
3. On various file system configurations to confirm the constants and paths are resolved correctly.
4. Manually inspected the outputs to ensure "true" and "false" are written to Bun.stdout as expected.

Screenshots (if appropriate):

N/A

[danstepanov]

@sammoore when you have a chance, can you review?