BUG: GHA possibly not writing build.json. Otherwise other bug leads to no RiffRaff deploy

[tylr-mk]

We've noticed this happen 2 times in approximately 2 weeks, but that's only from "known" failures to deploy. So I suspect there could be more cases.

We've observed intermittent failure where RiffRaff will not register a build and therefore not run Continuous Deployment following a RiffRaff GitHub Action. Best guess is there's some exit of the runtime before successful run of this block.

We have PR > Build 1 (on merge) > Build 2 (manually run this morning). Both builds create the Build number 11396. And the second manual run this morning triggered the RiffRaff build

Both exit 0. But pulling the tail of the logs shows only the successful run second prints "Upload Complete". Naive guess is that's this here.

1. unsuccessful

s3 sync: staging-JEjyzu/cloud-composer-deployment/dags/guardian/utils/teams.py -> ophan:data-lake:airflow/11396/cloud-composer-deployment/dags/guardian/utils/teams.py
s3 sync: staging-JEjyzu/riff-raff.yaml -> ophan:data-lake:airflow/11396/riff-raff.yaml

2. successful

s3 sync: staging-Cvk9Yh/cloud-composer-deployment/dags/guardian/utils/teams.py -> ophan:data-lake:airflow/11396/cloud-composer-deployment/dags/guardian/utils/teams.py
s3 sync: staging-Cvk9Yh/riff-raff.yaml -> ophan:data-lake:airflow/11396/riff-raff.yaml
Upload complete.
...