Is your feature request related to a problem? Please describe.

At present the only way to test custom versioned init packages is like the following:

mv zarf-init-amd64-3.5.1.tar.zst zarf-init-amd64-$(zarf version).tar.zst

Describe the behavior you'd like

• Keep the default behavior for looking for a zarf package that matches the current cli version
• Like with zarf package deploy allow the passing of a file path and use that path as the zarf package getting deploying.

Additional context

This is not a major blocking, seeing as we get (mostly) the same functionality from doing just a zarf package deploy... However for those of use that use custom package versions, unless we do the mv command above, we are unable to enable the proxy-registry (I mean seeing as it is an alpha feature, it makes sense we need to go through some hops to get it enabled)