Fix reversed errors.Is() argument order in CLI uploader

[bauerpawel]

Description

errors.Is(err, target) expects the error being checked first and the sentinel second; several calls in the CLI uploader (cmd/cli-uploader/Main.go, cmd/cli-uploader/cliconfig/cliconfig.go) had them swapped. Harmless today since none of the sentinels are themselves wrapped (so the initial equality check still matches either way), but fixed for correctness and to avoid silently breaking if a sentinel ever gets wrapped.

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Technical Details

• Database changes: No
• Storage backend affected: No
• Usage of AI: Yes — developed with Claude Code as a pair-programming assistant (spotted while reviewing the CLI error-handling code, applied the fix). I reviewed and tested all changes before submitting.

How Has This Been Tested?

• Unit Tests: go test ./... --tags=test,awsmock (full suite passes; cmd/cli-uploader has no test files, this is a straightforward argument-order correction with no behavior change under current conditions)
• Environment: Windows 11

Checklist

• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas. (n/a — no new logic, argument-order fix only)
• I have made corresponding changes to the documentation. (n/a — no behavior change)
• My changes generate no new warnings.

🤖 Generated with Claude Code

https://claude.ai/code/session_0168YUwGEzEHTqd9CwzXE53d

[Forceu]

Thanks