AZINTS-4118 Surface user actionable errors

[benjjs]

Motivation

We have some LFO errors that should be resolvable by the user. We should make these visible and easy to read in the UI.

Summary

Introduce a new status USER_ACTIONABLE_ERROR for errors that are user actionable. I feel comfortable not making this in some way a subtype of the ERROR status because we want to handle these quite differently.

All user actionable errors that we're aware of currently exist in the LFO portion of the script, where Altan has made them subtypes of UserActionRequiredError. When we catch an error in the step reporter, we first check if it is one of these. If so, we use the new status. We also use the simple string representation of the exception instead of a trace or rich representation, as the message to the user should be only the user-readable portion we include as the explicit error message.

As a result, we may need a subsequent diff to update some error messages to be more complete and actionable. Ideally they should consist of 2 brief sentences:

1. Explaining in a few words what the problem is.
2. Telling the user how to solve it.

I've also removed some error catching and re-raising logic in the LFO steps. This was nuking exception types, and shouldn't be necessary as the status reporter context manager itself adds some context to exceptions that are intended for our eyes.

Testing

See https://github.com/DataDog/web-ui/pull/243696

[agulen]

lgtm, i'll do a pass over all the user actionable LFO errors to make sure we're showing user-friendly messages