Unbreak upgrade CI tests by removing set -u from shell scripts | SKIP UPGRADE | SKIP UPDATE CHECK

General MR

Summary

Example failure: https://repo1.dso.mil/big-bang/product/packages/argocd/-/jobs/37729613#L576

set -u inside this script leads to failures in the upgrade job as several library functions in pipeline-templates are written to check for the existence of potentially missing variables. There's probably a clean way for me to set +u before my code goes out of scope here so as to avoid breaking the upgrade job but I can't think of it right now.

Relevant logs/screenshots

See previous failure at https://repo1.dso.mil/big-bang/product/packages/argocd/-/jobs/37729613#L576

../pipeline-repo/library/package-functions.sh: line 162: PROJECT_NAME: unbound variable

Linked Issue

N/A

Upgrade Notices

N/A