Refactor exit code handling and error reporting

[osterman]

what

• Unified Exit Code Handling: Replaced multiple methods of handling exit codes with a consistent approach using errUtils.GetExitCode(). This ensures that subcommands correctly report their exit codes, especially for errors like terraform plan -detailed-exitcode (exit code 2) or shell commands with specific exit codes.
• Standardized Error Reporting: Migrated all instances of cockroachdb/errors.WithHint*() to use the errUtils.Build() pattern for constructing errors with explanations and hints. This centralizes error building and improves consistency.
• Improved Shell Command Exit Code Extraction: The ShellRunner utility now correctly captures and preserves specific exit codes from shell commands, wrapping them in errUtils.ExitCodeError. This prevents generic error codes from masking the true exit status of shell commands.
• Terraform Workspace Handling: Corrected the logic for handling Terraform workspace selection errors. If a workspace doesn't exist (exit code 1), Atmos now attempts to create it, improving workflow robustness.
• Workflow Error Handling: Updated workflow_utils.go to correctly identify and handle errUtils.ExitCodeError as a known workflow error, preventing unnecessary re-wrapping or reporting of already handled subcommand failures.
• Testing & Snapshots: Updated test cases and snapshots to reflect the new error messages and exit code handling, including changes in TestCLICommands_atmos_circuit-breaker.stderr.golden and new test cases for exit-codes.yaml.
• Dependency Updates: Minor updates to AWS SDK versions in go.mod.

why

• Consistency and Maintainability: Standardizing exit code handling and error reporting makes the codebase more consistent, easier to understand, and maintainable.
• Accurate Error Propagation: Ensuring that specific exit codes from subcommands (like shell commands or Terraform) are preserved and reported accurately is crucial for debugging and for downstream tools that rely on these exit codes (e.g., CI/CD pipelines).
• Robustness: Improved handling of Terraform workspace errors makes workflows more resilient by automatically creating missing workspaces.
• Reduced Complexity: Consolidating error building patterns simplifies error management and reduces potential for inconsistencies.

[mergify]

Important

Cloud Posse Engineering Team Review Required

This pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes.

To expedite this process, reach out to us on Slack in the #pr-reviews channel.