Fix: sed portability and compatibility issue for the bundle commitSha image

[shivakunv]

https://github.com/NVIDIA/gpu-operator/actions/runs/20362800010/job/58514956441 : The CI pipeline failed after merging to main: #1898 from NVIDIA/bundlecommitsha : Tag git commit sha with bundle image

https://github.com/NVIDIA/gpu-operator/actions/runs/20364821808/job/58518239572 : Pipeline was reproduced

https://github.com/NVIDIA/gpu-operator/actions/runs/20364821808/job/58518239572: Pipeline passed with the new change

Please refer to the links below for details on the bug and compatibility issues with sed:

1. https://www.baeldung.com/linux/sed-error-no-such-file-or-directory
2. https://stackoverflow.com/questions/67086574/no-such-file-or-directory-when-using-sed-in-combination-with-find

sed -i '' -e 's|ghcr.io/nvidia/gpu-operator:[^ "]*|ghcr.io/nvidia/gpu-operator:${{ env.COMMIT_SHORT_SHA }}|g' bundle/manifests/gpu-operator-certified.clusterserviceversion.yaml : This command works only on Mac OS.

sed -i'' -e 's|ghcr.io/nvidia/gpu-operator:[^ "]*|ghcr.io/nvidia/gpu-operator:${{ env.COMMIT_SHORT_SHA }}|g' bundle/manifests/gpu-operator-certified.clusterserviceversion.yaml : This works for both MacOS and Linux, creates a backup file with a -e extension on macOS

sed -i -e 's|ghcr.io/nvidia/gpu-operator:[^ "]*|ghcr.io/nvidia/gpu-operator:${{ env.COMMIT_SHORT_SHA }}|g' bundle/manifests/gpu-operator-certified.clusterserviceversion.yaml : This works only on Linux, not Mac OS.

[coveralls]

coverage: 23.552%. remained the same
when pulling 9d84555 on commitsha
into 9ffbac0 on main.

[coveralls]

coverage: 23.552%. remained the same
when pulling 76dfef9 on commitsha
into 9ffbac0 on main.

[coveralls]

coverage: 23.552%. remained the same
when pulling a73f0f0 on commitsha
into 208ab8c on main.

[rahulait]

LGTM. If additional file creation was an issue, we could have also used yq. For now, this also looks good to me.

[shivakunv]

LGTM. If additional file creation was an issue, we could have also used yq. For now, this also looks good to me.

That won't be an issue since we have a Linux runner for CI/CD, so a local file won't be created. A local file will only be created if we use Mac-OS, such as during local testing.

[rajathagasthya]

/ok-to-test a73f0f0