[Bug] GraphQL requests do not properly support custom auth/TLS error status codes

[andrewazores]

Current Behavior

#350 + #294

"Normal" HTTP API requests that result in a JMX auth failure or JMX SSL/TLS failure result in API response status codes 427 and 502, respectively. These trigger the web-client to display a modal informing the user what went wrong and how they can fix it. When these same failures occur within a GraphQL context however, this happens instead:

Expected Behavior

Either the GraphQL API response status code should match and be 427/502 directly, or else the web-client should know how to handle GraphQL responses, unwrap them, and treat them the same way as 427/502 responses.

This should not apply to the Topology view - here these warnings should be ignored and no modals should appear. Notifications might appear, but if it's feasible, they should be suppressed. Instead, the yellow warning indication decorators should appear on the affected targets, and clicking each target to examine it should reveal some information on how the user can handle the problem (similar to what the modal would do).

Steps To Reproduce

No response

Environment

No response

Anything else?

No response