Jobs triggered from prefect-databricks should be cancelled when the parent flow run is cancelled

[masonmenges]

Describe the current behavior

Currently if an external job is triggered through prefect-databricks and the parent run that triggered the job is cancelled the external job continues to execute as there is no mechanism built in to ensure the external process is also terminated despite it originating from a prefect flow run.

Describe the proposed behavior

External Jobs/Processes triggered from flows within prefect-databricks are cancelled/terminated when possible if the originating flow run is also cancelled/terminated.

Example Use

No response

Additional context

No response