fix(eco): Report integration config errors to users when testing actions

[GabeVillalobos]

Adds a new exception type for reporting when showing users errors. These are distinct from form errors as they derive from configuration issues on the user side, but cannot be attributed to a specific field.

Updates ACI handling to consistently report exceptions in the same manner as our current rule actions.

[seer-by-sentry]

Potential bug: The code attempts to access e.id on an exception object, but standard exceptions lack an id attribute, which will cause an AttributeError.

• Description: In the except Exception as e block, the code calls sentry_sdk.capture_exception(e) but then attempts to format an error message using e.id. Standard Python exception objects do not have an id attribute, so this will raise an AttributeError. This new, unhandled exception occurs within the exception handler itself, causing the request to fail with a 500 error instead of returning the intended user-friendly message about the original problem. The correct implementation, seen elsewhere in the codebase, is to use the return value of sentry_sdk.capture_exception(e).

• Suggested fix: Capture the return value of sentry_sdk.capture_exception(e) and use it in the appended error message. Change the code to error_id = sentry_sdk.capture_exception(e) and then action_exceptions.append(f"An unexpected error occurred. Error ID: '{error_id}'").
  _{severity: 0.85, confidence: 0.98}

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.