Fix: Malformed error message formatting in makeMessage() function

[ac-mmi]

This PR fixes an issue with the library where the message field in the error response from the API was not properly formatted as valid JSON. The makeMessage() function in the error.ts file was updated to ensure that error messages are formatted correctly, allowing developers to parse them without encountering JSON parsing issues.

Solution:

1. The makeMessage() function in the error.ts file was updated to properly format the message string as valid JSON.
2. The formatting now includes necessary escape characters and ensures the string follows valid JSON syntax.
3. This ensures that the error message can be parsed by developers using JSON.parse() without any errors.

Fixes #1140

[nsaiprakash90]

Could we extract the error message formatting logic into a separate function for better readability and maintainability?

function formatErrorMessage(error: any): string {
    if (!error) return '';

    if (typeof error.message === 'string') {
        return error.message
            .replace(/'/g, '"') // Convert single quotes to double quotes
            .replace(/\(\s*([^()]+?)\s*\)/g, (_, content) => `[${content.split(/\s*,\s*/).join(', ')}]`);
            // Convert tuples of any length to arrays
    }

    return JSON.stringify(error.message ?? error);
}

Additionally, if we have existing tests, could we add test cases for the change?

[ac-mmi]

i made a separate function for formatmessage inside the class

[ac-mmi]

@nsaiprakash90 I couldn't find any tests specifically targeting the APIError class

[nsaiprakash90]

This looks great, thanks!

[RobertCraigie]

Thanks for the PR and really sorry for the delayed review.

Could you share some examples of the error messages before and after your change? I don't quite see how this will make a meaningful improvement? I'm going to close this for now but please re-open if you'd like this to get another review.