Standardize daily/weekly/... runners

[TyHil]

Makes a standard approach to running api-tools on GCP at some frequency, docs on how it works are here and copied below:

The deploy.yml GitHub action runs on push to develop and build an api-tools image on GCP using the Dockerfile. Then it sets the specified jobs to use this new image.

When a job runs (based on a scheduled trigger) it starts with the runners/setup.sh script which just sets up environment variables from GCP secrets. Then based on an environment variable from the runner's config it chooses another script to run, like runners/daily.sh, which specifies which api-tools commands to run.

This allows us to have one GCP job and one scripts file per running frequency.

Right now we only have a daily runner but this should make it easy to add more with varying frequency and commands.

Note: once merged I'll delete the old jobs and images. (And we'll see if the GitHub action still works)

[mikehquan19]

Setup looks good to me. @TyHil will check again if actions still work after merging. If anything, we can go from there.