Chore/trigger rebuild of lambda zips

[timburke-hackit]

Includes formatting changes to the scripts to trigger the null_resource - they remain functionally identical.

First run scenario:

• Source files are changed, so null_resource triggers
• Dependencies get installed
• Zip file is created with both source files and dependencies
• This complete zip file gets uploaded to S3

Subsequent runs (no source changes):

• Same source files produce the same dir_sha1 hash
• null_resource doesn't trigger (since the hash is unchanged)
• A local zip gets created with only source files (no dependencies)
  • this is what was being uploaded and resulting in failures
• Terraform sees that source_hash hasn't changed in the state, so it won't update the S3 object
• Lambda continues using the original, complete zip from S3

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud