feat(ISV-5571): ignore SBOM-related task errors in rh-advisories

[wcheang]

Describe your changes

Failing to process or upload SBOMs should not fail the whole rh-advisories pipeline. This change ensures that the pipeline will continue even if there are errors in the SBOM-related tasks.

Relevant Jira

https://issues.redhat.com/browse/ISV-5571

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 have bumped the task/pipeline version string and updated changelog in the relevant README
• I read CONTRIBUTING.MD and commit formatting

[openshift-ci]

Hi @wcheang. Thanks for your PR.

I'm waiting for a konflux-ci member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[johnbieren]

I am cool with this change, but let's see if Martin is too. It would be nice to set this to yellow (I think that is the unstable status in tekton?) in the pipeline visualization to alert users something happened here, but given I don't know how to do that, not too fair for me to ask you to 🙂

[johnbieren]

/ok-to-test

[jedinym]

@johnbieren any idea why the tests still haven't started?

[johnbieren]

Hmm, no, but retest should start them

[johnbieren]

/retest

[johnbieren]

/retest

[mmalina]

I am cool with this change, but let's see if Martin is too. It would be nice to set this to yellow (I think that is the unstable status in tekton?) in the pipeline visualization to alert users something happened here, but given I don't know how to do that, not too fair for me to ask you to 🙂

I don't think Tekton has any option to show a taskrun as yellow. AFAIK, it's a Konflux feature, but not really applicable for our use case, see my comment here: #786 (comment)

[mmalina]

/ok-to-test