volume delete: allow prefix for ID

[tgross]

The volume delete command doesn't allow using a prefix for the volume ID for either CSI or dynamic host volumes. Use a prefix search and wildcard namespace as we do for other CLI commands.

Ref: https://hashicorp.atlassian.net/browse/NET-12057

---

Example of use:

$ nomad volume create ./internal-plugin.volume.hcl
==> Created host volume internal-plugin with ID aeea91a0-06df-c16e-5403-ff82a2f28fd4
  ✓ Host volume "aeea91a0" ready

    2025-01-31T15:55:14-05:00
    ID        = aeea91a0-06df-c16e-5403-ff82a2f28fd4
    Name      = internal-plugin
    Namespace = default
    Plugin ID = mkdir
    Node ID   = b4611abd-d4a8-c83a-b05e-7d9f5b44a179
    Node Pool = default
    Capacity  = 0 B
    State     = ready
    Host Path = /run/nomad/dev/data/host_volumes/aeea91a0-06df-c16e-5403-ff82a2f28fd4

$ nomad volume delete -type host aeea91a0
Successfully deleted volume "aeea91a0-06df-c16e-5403-ff82a2f28fd4"!

[gulducat]

lgtm!

[gulducat]

I'm not seeing test coverage for this, and if it were handled incorrectly (a bug introduced later?), it could cause external persistent state to be lost.

[tgross]

We don't have any CLI unit coverage for the volume delete command and very little meaningful coverage of the CSI HTTP APIs at all for that matter, because of the setup requirements. We pretty much just test the routing and that's about it; the functionality is being covered in the RPC handler tests. The juice isn't worth the squeeze for coverage here.

[gulducat]

👍

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.