limactl help and info flag should show available plugins

[olamilekan000]

change adds functionality to display Plugins in the info and list commands

Fixes #3608 (comment)

[jandubois]

I haven't looked at the docs changes, but here is some feedback on the code.

[jandubois]

Docs review

[AkihiroSuda]

BATS failing

ok 38 setting both allow list and block list generates a warning in 138ms
not ok 39 limactl info includes the default block list in 124ms
# (in test file hack/bats/tests/preserve-env.bats, line 152)
#   `run -0 limactl yq '.shellEnvBlock[]' <<<"$output"' failed, expected exit code 0, got 1
# time="2025-09-17T09:21:44Z" level=warning msg="Plugin discovery: failed to scan directory /snap/bin: open /snap/bin: no such file or directory"
# time="2025-09-17T09:21:44Z" level=warning msg="Plugin discovery: failed to scan directory /home/runner/.local/bin: open /home/runner/.local/bin: no such file or directory"
# time="2025-09-17T09:21:44Z" level=warning msg="Plugin discovery: failed to scan directory /home/runner/.config/composer/vendor/bin: open /home/runner/.config/composer/vendor/bin: no such file or directory"
# time="2025-09-17T09:21:44Z" level=warning msg="Plugin discovery: failed to scan directory /snap/bin: open /snap/bin: no such file or directory"
# Error: bad file '-': yaml: mapping values are not allowed in this context
# ===== protect =====
ok 40 create dummy instance in 66ms

https://github.com/lima-vm/lima/actions/runs/17775630264/job/50573056648?pr=4009

[jandubois]

I think I mentioned this before that you should use the path to the plugin from the discovery code and not call exec.LookPath, which might find a different version of the plugin in case there are bugs in the discovery algorithm.

Use the same list in both places to make sure the behaviour is always in sync!