[AZINTS-4595] Remove Error Traceback from UserActionRequiredError and UserRetriableError messages

[mshvartsberg]

Motivation

When an Azure quickstart script encounters an error, it reports status updates to Datadog. Some error classes (subclasses of UserActionRequiredError and UserRetriableError) were appending raw Azure CLI output to their messages via format_error_details(), which may contain PII that should not be sent to Datadog.

Changes

• az_shared/errors.py: Removed all format_error_details(error_message) calls from UserActionRequiredError subclasses so only the static, user-facing user_action_message is included. Fixed AzCliNotAuthenticatedError to use a static message instead of passing error_message as the user action. Removed the now-unused format_error_details helper.
• script_status.py: Changed the UserRetriableError handler in report_step() to report e.user_action_message instead of traceback.format_exc(), matching the pattern already used for UserActionRequiredError.
• test_script_status.py: Updated test_user_actionable_error and test_user_retriable_error to reflect the new messages (no raw error details appended).

Testing

• Unit tests in test_script_status.py cover the updated behavior.
• Full verification that no PII reaches Datadog will be confirmed once the error logging pipeline (AZINTS-4597, AZINTS-4596) is deployed and logs are visible on the dashboard.
• Both end to end flows for configure log forwarding and app registration still work.