Octue

Summary
Add the ability to provide build secrets in `octue.yaml` to be used as build args in the deployers' docker build step. This allows us to remove manual `cloudbuild.yaml` files from some repositories, reducing manual work and repetition, and increasing deployment resilience.

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([329](https://github.com/octue/octue-sdk-python/pull/329))

Enhancements
- Add ability to provide build secrets in `octue.yaml`
- Require services to be specified under services key in `octue.yaml`
- Remove redundant passing of image URI template to deployers

Refactoring
- Rename `worker_machine_type` to `machine_type` in `octue.yaml`

<!--- END AUTOGENERATED NOTES --->

<!--- START AUTOGENERATED NOTES --->
Contents ([325](https://github.com/octue/octue-sdk-python/pull/325))

Operations
- Ignore codecov upload failure in release workflow

<!--- END AUTOGENERATED NOTES --->

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([322](https://github.com/octue/octue-sdk-python/pull/322))

Enhancements
- Allow service account, machine type, and maximum instances options in `octue.yaml` for Dataflow deployments

Fixes
- Always use latest `octue-sdk-python` image in `DataflowDeployer`

Refactoring
- Move Cloud-Run-only optional `octue.yaml` file options out of `BaseDeployer` and into `CloudRunDeployer`
- Create pipeline options from a dictionary
- Remove `runner` parameter from `create_streaming_job`

Operations
- Tag latest image as `latest` in docker workflow

<!--- END AUTOGENERATED NOTES --->

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([320](https://github.com/octue/octue-sdk-python/pull/320))

Operations
- Replace `cloudbuild.yam`l with GitHub action to build and push the `octue-sdk-python` image

<!--- END AUTOGENERATED NOTES --->

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([319](https://github.com/octue/octue-sdk-python/pull/319))

Fixes
- Push `octue-sdk-python` image to public Docker Hub repository in `cloudbuild.yaml`
- Use latest `octue-sdk-python` image in generated Cloud Build step in `DataflowDeployer`
- Use the image URI template in `cloudbuild.yaml` file generation instead of a static image name
- Split deploying a Dataflow job from creating and triggering a build trigger in `DataflowDeployer`

Refactoring
- Store required environment variables in dictionary in `BaseDeployer`

<!--- END AUTOGENERATED NOTES --->

Summary
When deploying a service to Dataflow, add future automated Dataflow deployment to the build trigger. This removes the need to manually re-deploy a service to Dataflow using `octue-app dataflow deploy` each time the build trigger is run.

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([318](https://github.com/octue/octue-sdk-python/pull/318))

Enhancements
- Add Cloud Build step to `DataflowDeployer` to deploy a job to Dataflow
- Stop deploying jobs to Dataflow directly from local machine by default in `DataflowDeployer`
- Add option to `deploy dataflow` CLI command to skip creating and running the build trigger and only deploy the Dataflow job
- Allow `Topic` to be instantiated without a namespace

Fixes
- Make `BaseDeployer` wait for queued builds instead of raising an error
- Ensure `DataflowDeployer._deploy_streaming_dataflow_job` creates jobs if they don't exist when the `update` parameter is `True`
- Ensure the Dataflow service topic exists before deploying a job

Refactoring
- Combine `BaseDeployer._run_build_trigger` and `BaseDeployer._wait_for_build_to_finish`

Operations
- Add `.dockerignore` file
- Add `Dockerfile` and `cloudbuild.yaml` for the `octue` package

<!--- END AUTOGENERATED NOTES --->