fix: kubectl argument too long when updating release cr

[arewm]

Describe your changes

Most of the development and CI has been done assuming smaller Snapshots. When releasing larger snapshots (i.e. 180 components), we start to encounter issues ranging from higher likelihood to hit timeouts, increased memory consumption, and long strings being processed.

This PR is focused on fixing an issue where update-cr-status could not process large snapshots, namely because we were passing too much information to kubectl.

Partially addresses: KONFLUX-8821 in conjunction with #1218, #1219, #1220

Assisted-by: Cursor
Signed-off-by: arewm [email protected]

Relevant Jira

Checklist before requesting a review

• I have marked as draft or added do not merge label if there's a dependency PR
  • If you want reviews on your draft PR, you can add reviewers or add the release-service-maintainers handle if you are unsure who to tag
• My commit message includes Signed-off-by: My name <email>
• I read CONTRIBUTING.MD and commit formatting
• I have run the README.md generator script in .github/scripts/readme_generator.sh and verified the results using .github/scripts/check_readme.sh

[FilipNikolovski]

lgtm apart from the lint errors.

[johnbieren]

This fails gitlint, yamllint, unit tests, and has a rebase conflict

[arewm]

Converting to draft as I need to check to see whether #1214 resolves this same issue.

[arewm]

This PR is ready for review again. #1214 duplicated much of the work for this PR, so now it is distilled down just to the status update issue.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[johnbieren]

⚠️ Warning: Could not get component PR from annotations: {"pac":{"state":"error","error-id":74,"error-message":"74: Access token is unrecognizable by GitHub"},"message":"done"}
Requesting a new configure-pac...
component.appstudio.redhat.com/rhtap-service-push-b8455b79 annotate
Waiting 10 seconds before retry...
Initialization check attempt 58/60...

I haven't seen that before

[johnbieren]

/retest

[konflux-ci-qe-bot]

@arewm: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name	Status	Rerun command	Build Log	Test Log
push-to-external-registry-e2e-test-go-jslpl	Failed	/retest	View Pipeline Log	View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

1. Install ORAS (see the ORAS installation guide).
2. Download artifacts with the following commands:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service-catalog:push-to-external-registry-e2e-test-go-jslpl

Test results analysis

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

➡️ [failed] [It] [release-pipelines-suite Push to external registry] Post-release verification verifies that Release PipelineRun should eventually succeed [release-pipelines, push-to-external-registry]

Click to view logs

Error when waiting for a release pipelinerun for release ex-registry-mbfe/snapshot-sample-ndyw-wtdgd to finish
Expected success, but got an error:
    <*errors.errorString | 0xc000efc9e0>: 
    Pipelinerun 'managed-m4f6c' didn't succeed
    Logs from failed container 'managed-m4f6c-verify-conforma/step-show-config': 
    jq: error: Could not open file /tekton/home/report-json.json: No such file or directory
    
    {
        s: "Pipelinerun 'managed-m4f6c' didn't succeed\nLogs from failed container 'managed-m4f6c-verify-conforma/step-show-config': \njq: error: Could not open file /tekton/home/report-json.json: No such file or directory\n",
    }

---