hostmgr vm start [name] should unpack matching local package

Typically the files for a VM are in one of two states:
1. Not present locally and only on S3
2. Present locally in `/opt/ci/vm-images` in the form of a compressed package and extracted template, `vmname.vmtemplate.aar` and `vmname.vmtemplate` respectively.

There's a third state that's possible and made be preferred with future enhancements:
- `vmname.vmtemplate.aar` exists locally
- `vmname.vmtemplate` does not exist locally because we needed to free up space

Current behavior in this third state:

1. `hostmgr vm start vmname` fails
2. `hostmgr vm fetch vmname` extracts the `vmname.vmtemplate.aar` local package
3. `hostmgr vm start vmname` succeeds

Future behavior:

1. `hostmgr vm start vmname` succeeds on the first try because it found a matching local archive that could be extracted

Start at the hostmgr vm start and hostmgr vm fetch command entry points and trace how files in /opt/ci/vm-images are detected and extracted. The change is complete when vm start finds a matching .vmtemplate.aar without an extracted template and extracts it before starting the VM.

Written by the indexing model from the issue text.