[BUG] Removing docker from the options + running hl:babashka:sync results in download_pods: command not found

[benjamin-asdf]

Describe the bug

{:warning "clashing jar item", :path "native-agents-payloads/1.edn", :strategy :noop}
{:warning "could not find classpath entry", :path "/home/benj/.gitlibs/libs/org.babashka/spec.alpha/8df0712896f596680da7a32ae44bb000b7e45e68/src/main/java"}
{:warning "could not find classpath entry", :path "/home/benj/.gitlibs/libs/org.babashka/spec.alpha/8df0712896f596680da7a32ae44bb000b7e45e68/src/main/resources"}
{:warning "clashing jar item", :path "META-INF/versions/11/module-info.class", :strategy :noop}
{:warning "clashing jar item", :path "META-INF/versions/11/module-info.class", :strategy :noop}
[holy-lambda] Babashka pods found! Syncing babashka pods. Pods should be distributed via a layer which points to .holy-lambda/pods
bash: line 1: download_pods: command not found

To reproduce

Here is my bb.edn, run babashka:sync

 ["src" "resources"]
 :deps {io.github.FieryCod/holy-lambda-babashka-tasks
        {:git/url "https://github.com/FieryCod/holy-lambda", :sha "1469bb96b85c2c65a52df9e3a4914dde1b4c816f", :deps/root "./modules/holy-lambda-babashka-tasks"}
        io.github.FieryCod/holy-lambda {:mvn/version "0.6.6"}

        org.babashka/spec.alpha {:git/url "https://github.com/babashka/spec.alpha"
                                 :git/sha "8df0712896f596680da7a32ae44bb000b7e45e68"}
        org.clojure/core.specs.alpha {:mvn/version "0.2.62"}
        com.rpl/specter {:mvn/version "1.1.4"}

        hato/hato {:mvn/version "0.8.2"}}

 :pods {org.babashka/aws {:version "0.1.2"}
        org.babashka/buddy {:version "0.2.0"}}

 ;; Minimal babashka version which should be used in conjuction with holy-lambda
 :min-bb-version "0.3.7"

 :holy-lambda/options {
                       :backend
                       {
                        ;; Babashka pods should be shipped using AWS Lambda Layer
                        ;; Check this template https://github.com/aws-samples/aws-lambda-layers-aws-sam-examples/blob/master/aws-sdk-layer/template.yaml
                        ;; and official docs https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-layers.html
                        ;; CodeUri should be `.holy-lambda/pods`
                        ;; For now pods should be declared in `bb.edn`. See: https://github.com/babashka/babashka/issues/768#issuecomment-825016317
                        ;;
                        ;; `IMPORTANT:` 3rd party babashka compatible libraries should be distributed as a layers (CodeUri: .holy-lambda/bb-clj-deps)

                        :pods
                        {org.babashka/aws {:version "0.1.2"}
                         org.babashka/buddy {:version "0.2.0"}}}}

 :tasks {:requires            ([holy-lambda.tasks])
         local-invoke (shell {:extra-env {"AWS_PROFILE" "datalake-admin"}} "sam" "local" "invoke" "SheetLambdaFunction")
         hl:babashka:sync     holy-lambda.tasks/hl:babashka:sync
         hl:doctor            holy-lambda.tasks/hl:doctor
         hl:clean             holy-lambda.tasks/hl:clean
         hl:update-bb-tasks   holy-lambda.tasks/hl:update-bb-tasks
         hl:version           holy-lambda.tasks/hl:version}}```


**Extra information:**

 - `bb stack:doctor` output:
[holy-lambda] Executable UNKNOWN does not exists! Using fallback: java instead! Did you set up GRAALVM_HOME?
[holy-lambda] Executable UNKNOWN does not exists! Using fallback: native-image instead! Did you set up GRAALVM_HOME?