fixed error handling for passport api

[fatimaaurangzeb0640]

Description

Fixed error handling for passport api. The error response for passport api looks like this:

SafepayAuthenticationError: unauthorized, strategies/union: [strategies/jwt_client: missing jwt token, strategies/secret: could not fetch client, error: Resource with this identifier not found] at /Users/fatima/Code/test-app/node_modules/@sfpy/node-core/cjs/RequestSender.js:27:27 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { type: 'SafepayAuthenticationError', status: 401 }

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• UI change (Front-end UI update without breaking changes or business logic)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Description

1. What is the current behavior? (You can also link to an open issue here)

2. What is the new behavior (if this is a feature change)?

3. Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[ziyadparekh]

why do we want to print error.message? wouldn't that always just be fail? shouldn't it print the actual message inside the errors array?