require release type in utility scripts

[amcmanus]

This is an initial solution to a feature request that would use release type asset directories for vx-iso rather than using a shared directory that is overwritten each time. This enables installing different release types without having to extract the image each time you switch between release types.

While this adds some level of convenience, it adds to the complexity of the local user environment when managing different releases. For example, a user could extract a field release with the admin release type. That would put a valid field release under the admin assets directory structure. If an older field release were still present, it's possible that release could then be installed instead of the most recently extracted. Similarly, a user could intend to install an admin release, not realizing a field release was most recently extracted there by mistake.

@arsalansufi, I don't want to over-rotate on this, but I'd be interested in whether you think there's value in taking the time and effort to consider something like embedding the release type in a release to help with some of this basic validation? There's probably a follow-up question on whether we should add another check for the release version for many of the same reasons.

[arsalansufi]

Super delayed review but better late than never

[arsalansufi]

Hm so I don't think that we should default the value to field. Because then, if you forget to specify the second param but are extracting an admin vx-iso image, you're gonna persist it at the wrong location silently. I think that the second param should always be explicitly specified. I'm happy with this approach if we drop the default/fallback value.

[amcmanus]

This will close votingworks/vxsuite#7197