Consider adding debug logs to allow easier debugging

[pmalek]

Problem statement

Recently, I've observed several failures when running this plugin (with mise) on GitHub Actions, e.g.:

https://github.com/Kong/kong-operator/actions/runs/17239005077/job/48910800121

DEBUG ARGS: /home/runner/.local/share/mise/bin/mise plugin install --yes -q markdownlint-cli2
DEBUG config: ~/work/kong-operator/kong-operator/.mise.toml
installing markdownlint-cli2
DEBUG asdf_plugin[markdownlint-cli2]:install "https://github.com/paulo-ferraz-oliveira/asdf-markdownlint-cli2.git"
INFO  plugin:markdownlint-cli2 clone https://github.com/paulo-ferraz-oliveira/asdf-markdownlint-cli2.git
DEBUG cloning https://github.com/paulo-ferraz-oliveira/asdf-markdownlint-cli2.git to /home/runner/work/kong-operator/kong-operator/bin/plugins/markdownlint-cli2 with gix
DEBUG starting new connection: https://github.com/
DEBUG current sha for "/home/runner/work/kong-operator/kong-operator/bin/plugins/markdownlint-cli2": 6d14d9f
INFO  plugin:markdownlint-cli2 ✓ https://github.com/paulo-ferraz-oliveira/asdf-markdownlint-cli2.git#6d14d9f
DEBUG Version: 2025.8.20 linux-x64 (2025-08-22)
DEBUG mkdirp: "/home/runner/.cache/mise/.auto_prune"
DEBUG pruning old cache files, this behavior can be modified with the MISE_CACHE_PRUNE_AGE setting
DEBUG ARGS: /home/runner/.local/share/mise/bin/mise install -q markdownlint-cli2@0.18.1
DEBUG config: ~/work/kong-operator/kong-operator/.mise.toml
INFO  mise 2025.8.20 by @jdx – install
DEBUG install_some_versions: markdownlint-cli2@0.18.1
DEBUG $ /home/runner/work/kong-operator/kong-operator/bin/plugins/markdownlint-cli2/bin/list-all 
INFO  markdownlint-cli2@0.18.1 install
DEBUG EnvResults { env: ["MISE_DATA_DIR"] }
INFO  markdownlint-cli2@0.18.1 bin/download
INFO  markdownlint-cli2@0.18.1 ~/work/kong-operator/kong-operator/bin/plugins/markdownlint-cli2/bin/download
DEBUG $ ~/work/kong-operator/kong-operator/bin/plugins/markdownlint-cli2/bin/download 
INFO  markdownlint-cli2@0.18.1 * Downloading markdownlint-cli2 release 0.18.1...
ERROR ~/work/kong-operator/kong-operator/bin/plugins/markdownlint-cli2/bin/download failed
Error: 
   0: Failed to install tool: markdownlint-cli2@0.18.1

      markdownlint-cli2@0.18.1: 
         0: failed to install asdf:markdownlint-cli2@0.18.1
         1: ~/work/kong-operator/kong-operator/bin/plugins/markdownlint-cli2/bin/download exited with non-zero status: exit code 1

      Location:
         src/plugins/script_manager.rs:184

      Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
      Run with RUST_BACKTRACE=full to include source snippets.

Location:
   src/toolset/mod.rs:256

Version:
   2025.8.20 linux-x64 (2025-08-22)

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.

Even though mise itself provides debug logs, this plugin itself doesn't which makes it hard to find the culprit of CI failures.

Proposed solution

Add --verbose flag to the npm pack invocation at

asdf-markdownlint-cli2/lib/utils.bash

Line 62 in 6d14d9f

npm pack --silent "${TOOL_NAME}@${version}" --pack-destination "$destination" >/dev/null