CLI Enhancement: Add glob support for status and stop commands

I ran into an issue where I had a dozens of dispatch jobs stuck in "running" (tasks were "pending") due to a missing configuration in the app code (not Nomad's fault).

I wanted to shut them down and wait for a new deploy to fix the issue, but had to copy each of the invocations separately to "nomad stop" them.

In this case, it would be great to use standard glob logic to act on them all. This was a test cluster, so I only had dozens to deal with, but could see alot of work to clean up a production environment.

Based on gitter chat with @schmichael, the "stop" and "status" commands could likely benefit from glob support.

Bonus points for a confirmation prompt before executing the action.

Start with the Nomad CLI entry points for the status and stop commands and trace how job names are currently accepted. Define how standard glob matching should select jobs, whether the optional confirmation prompt applies to stop, and verify that both commands handle matching and non-matching patterns as intended.

Written by the indexing model from the issue text.