Dbtc

Fixed

- In progress runs weren't properly being cancelled within the `trigger_autoscaling_ci_job` method. In addiiton to checking if the job has an in progress run, this method will now also check if there is a run in a "running" state for the PR ID given in the payload. This will ensure that a single PR can only have one run occuring at a given time (this wasn't the case in 0.3.0).

Added

- `trigger_autoscaling_ci_job` method to the `cloud` property of the `dbtCloudClient` class.

Changed

- The restart from failure functionality has now been moved to it's own separate method, `trigger_job_from_failure`. You'll still be able to trigger a job using the `trigger_job` method.

Fixed

- Non json artifacts are now able to be retrieved from `get_run_artifact`

Fixed

- Bad url configuration for `create_job` method

Fixed

- Global CLI args `--warn-error` and `--use-experimental-parser` were not being considered. If they were present in the command, the modified command would have been invalid. These are now included within the `modified_command` if present in the initial step's command.

Added

- `--full-refresh` flag is now being pulled in the `modified_command` if present in the initial step's command.

Fixed

- Checking for an invalid result "skip" instead of "skipped" when identifying nodes that need to be reran.