[Discover] fix error construction and retrieving status

[joshuali925]

Description

This is a follow up fix for #8565, in case response.data.body is an Error object, passing it to Error constructor calls String(Error) which returns [object object]. Additionally, if error.message is a valid JSON, the route will get status code from JSON.parse(error.message).status, which is not always present.

The PR changes error construction to use response.data.body.message if available, and uses error.status if status is not available in parsed JSON.

Issues Resolved

Screenshot

Testing the changes

Changelog

• skip

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.78%. Comparing base (78204a0) to head (ae58e67).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8807   +/-   ##
=======================================
  Coverage   60.78%   60.78%           
=======================================
  Files        3798     3798           
  Lines       90701    90701           
  Branches    14284    14284           
=======================================
  Hits        55135    55135           
  Misses      32067    32067           
  Partials     3499     3499           

Flag	Coverage Δ
Linux_1	29.05% <ø> (ø)
Linux_2	56.39% <ø> (ø)
Linux_3	37.65% <ø> (-0.01%)	⬇️
Linux_4	29.82% <100.00%> (ø)
Windows_1	29.06% <ø> (ø)
Windows_2	56.34% <ø> (ø)
Windows_3	37.66% <ø> (ø)
Windows_4	29.82% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.