Add ParseError to include rawBody and requestID for debugging purposes

[atainter]

Description

Some customers have reported receiving non-json responses from the workos API. These raise a syntax error when the Node.js ADK attempts to parse the json. This PR adds rawBody and requestID to a new ParseError exception for debugging purposes.

[greptile-apps]

Greptile Summary

This PR enhances error handling in the WorkOS Node.js SDK by introducing a new ParseError class to handle cases where non-JSON responses are received from the WorkOS API. The changes add important debugging information (raw response body and request ID) when JSON parsing fails.

The implementation involves:

1. Adding a new ParseError class that extends Error and implements RequestException
2. Modifying the HTTP methods (post, get, put) to capture and include debugging information when parsing fails
3. Adding a new handleParseError method to extract the raw response and request ID

This change will significantly improve debugging capabilities when investigating API response issues, particularly beneficial for support scenarios.

Confidence score: 5/5

1. This PR is very safe to merge as it only adds error handling improvements
2. The changes are well-contained, only affecting error handling paths, and can't impact successful API calls
3. No files need special attention as the changes are straightforward and well-implemented

_{2 files reviewed, 2 comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Ensure 500 is the correct status code for parse errors. Consider if 400 might be more appropriate since it's a client-side parsing issue.

[mattgd]

Thanks for adding this. Could we add a test to exercise the ParseError behavior?

[mattgd]

Thanks for implementing this!