Octue

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

Enhancements
- Raise more succinct error if `octue.yaml` file cannot be found in CLI command

Style
- Add line between built-in, third-party, and relative imports

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

Summary
Add the `octue-app deploy cloud-run` CLI command that can be run from the top-level of a repository containing an `octue` app to:
1. Create a build configuration
2. Create a build trigger
3. Build and deploy the app to Google Cloud Run as a service
4. Create and attach an Eventarc run trigger to the service

The command reads an `octue.yaml` file specifying required and optional arguments that control aspects of the build trigger and Cloud Run service.

**Note:** This command requires the Google Cloud CLI `gcloud` to be available - I still need to choose a way to ensure it is.

Possible solutions using a docker container include:
- Engineers running the command themselves from a local container
- Anyone (with permission) triggering a Google Cloud Function via the `octue` CLI
- Creating a GitHub app that listens for events on repositories its installed on and triggers the command based on these (longer term)

Information on the `gcloud` version used for developing this command:

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

Enhancements
- Allow kwargs to be passed to `Dataset.from_local_directory`

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

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

Enhancements
- Add analysis ID to log messages forwarded from child
<!--- END AUTOGENERATED NOTES --->

Summary
Add the ability to deploy services as Google Dataflow streaming jobs to allow greater freedom in machine specifications and analysis complexities/demands. Parents do not need to know whether a child is a Cloud Run service or a Dataflow service.

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

New features
- Add function and CLI command for deploying apps as Google Dataflow streaming pipeline services

Enhancements
- Add static methods for topic and subscription path generation without requiring `Topic` or `Subscription` instantiation

Fixes
- Allow response subscriptions to already exist in `Service.answer` so that questions can be re-asked if no delivery acknowledgement is received

Refactoring
- Move Cloud Run deployment module and Dockerfile into `cloud_run` subpackage
- Factor out Pub/Sub question answering function from Cloud Run `flask` app

Dependencies
- Temporarily downgrade to `google-cloud-pubsub==1.7.0`. This can be reverted when version `2.36.0` of `apache-beam` is released as it provides support for `google-cloud-pubsub>=2`

Style
- Ignore missing public docstring warning during pre-commit checks to allow docstrings to be added at the end of a pull request once new code is stable

Testing
- Move Cloud Run deployment tests into their own test module
- Change `RUN_DEPLOYMENT_TESTS` environment variable expected values to integers 0 and 1

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

Summary
Remove two `Dataset` methods that were deprecated 13 months ago. Also remove the `Loggable` mixin, which was causing confusion on how log messages should be emitted.

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([305](https://github.com/octue/octue-sdk-python/pull/305))
**IMPORTANT:** There is 1 breaking change.

Refactoring
- Remove `Loggable` mixin
- **BREAKING CHANGE:** Remove deprecated `Dataset.append` and `Dataset.get_files` methods

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