Rescue Http errors with given message

[Polo2]

4xx only, read http error message

This is a long term missing feature in the CLI
(noticed while implementing paywall and error payment_required with status 402 on Bump.sh API).

With this commit, when http error code is 4xx and not explicitly catched (400, 401, 404, 422),
we return the provided error message to the CLI user, with the status.

[Polo2]

Thanks dear review,
following your comments and a little more reflexion far from my keyboard, I rewrote the PR to something easier to review and merge:

There is already the info.length > 0 validation,
and generic message is raised when info is nil:
Unhandled API error (status: ${status}) (error: ${httpError}),
even if the error response had a message -> that's the case I want to fix in this PR!

In this PR, we add a default behavior (outside 400, 401, 404 and 422 explicit error codes),
to reuse the provde error message if it's possible.

Else, fallback to current behavior.

I pushed this in 2nd commit, WDYT?

[fbraure]

LGTM

[Polo2]

Thanks for the ✅ , I'll squash commits and fix the conflict before merging it

[paulRbr]

I would have kept the http status to have the same logic as the other errors :)

Suggested change

	static genericErrorFromMessage(error: Error): MessagesAndExitCode {
	return error.message ? [[error.message], 100] : [[], 100]
	}
	static genericErrorFromMessage(error: Error, status: number): MessagesAndExitCode {
	return [error.message ? [error.message] : [], status - 300]
	}