Add CI step for models script

[philmcmahon]

What does this change?

To support this change in AMIgo guardian/amigo#1607 to download whisperx models, this PR adds a CI step to add a new riffraff project which deploys the download-models script to a bucket in the deploy tools account where AMIgo can access it.

See this discussion for the motivation to publish to S3 via riffraff guardian/amigo#1607 (comment)

With this change, if we want to make a change to the download model script, the steps are:

• push to feature branch
• use riffraff to deploy the investigations::transcription-service-whisperx-model-fetch project to CODE/PROD
• If we deployed to CODE, update the 'stage' parameter set on the AMIgo recipe used for the whisperx workers to point at CODE
• Bake an AMI - it will fetch the script we deployed with riffraff

How to test

I've tested this using AMIgo CODE

[zekehuntergreen]

no CODE?

[philmcmahon]

oops!

[github-actions]

Deploy build 767 of investigations::transcription-service-whisperx-model-fetch to CODE

All deployment options

• Deploy build 767 of investigations::transcription-service-whisperx-model-fetch to CODE
• Deploy parts of build 767 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.