fix(cve): use base64 -w 0 to prevent newline-broken auth headers

base64 wraps output at 76 characters by default, which injects newlines
into the Authorization header when credentials are long enough. This
causes curl error 43 ("bad argument") and HTTP 000 responses.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: angaduom

workflows/cve-fixer/.claude/commands/cve.find.md

@@ -58,7 +58,7 @@ Report: artifacts/cve-fixer/find/cve-issues-20260226-145018.md
 
    ```bash
    JIRA_BASE_URL="https://redhat.atlassian.net"
-   AUTH=$(echo -n "${JIRA_EMAIL}:${JIRA_API_TOKEN}" | base64)
+   AUTH=$(echo -n "${JIRA_EMAIL}:${JIRA_API_TOKEN}" | base64 -w 0)
 
    # Retry once on network failure (curl exit code 000 = timeout/no response)
    for ATTEMPT in 1 2; do

workflows/cve-fixer/.claude/commands/cve.fix.md

@@ -527,7 +527,7 @@ This issue can be closed as 'Not a Bug / ${VEX_JUSTIFICATION}' if the above evid
    COMMENT_JSON=$(jq -n --arg body "$COMMENT_TEXT" '{"body": $body}')
 
    # Post comment via Jira API
-   AUTH=$(echo -n "${JIRA_EMAIL}:${JIRA_API_TOKEN}" | base64)
+   AUTH=$(echo -n "${JIRA_EMAIL}:${JIRA_API_TOKEN}" | base64 -w 0)
    curl -s -X POST \
      -H "Authorization: Basic ${AUTH}" \
      -H "Content-Type: application/json" \