Interceptor-like twist for a Babashka task runner

bb_task_interceptors.edn

;; For instance, build tasks produce garbage and an interceptor-like interface is a great match
;;
{:tasks {:build-something {:enter {:babashka/process ["bash" "-c" "touch file.txt"]}
                           :leave {:babashka/process ["bash" "-c" "rm file.txt"]}}}}

;; Clearer than splitting the task in two
;;
{:tasks {:create-file     {:babashka/process ["bash" "-c" "touch file.txt"]}
         :delete-file     {:babashka/process ["bash" "-c" "rm file.txt"]}
         :build-something {:babashka/args [:do :create-file
                                           :do :delete-file]}}}

;; More importantly, execution semantics could differ between :enter and :leaver
;;
;; Eg. Fail fast on :enter cycle (important tasks, all should succeed), just issue warning when task fails
;; in :leave cycle (since it's juste garbage cleaning and nothing crucial).
;;
;; Deserves more thought but acknowledging different phases with possibly different execution semantics would
;; be the dream declarative task runner as far as I am concerned.