Fixed issue identifying and parsing errors on client (SQL execution input)

[KyGuy2002]

The frontend currently expects "error" to be in the response json and the message to be at error.cause or error.message.

The exec endpoint actually returns it in this format: STATUS: 500 { code: 400, message: "error message here" }

Im not sure if this was due to a change that happened and broke this, or if it was never implemented in the first place, but I fixed it now.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 70e4d139d41fe4944a9b39d0b1a45e9aa0ac1195

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR