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

As Ezra I want to have a cleaner workflow for creating and testing packages during development so that I can test their logic and flow without having to run zarf p c and zarf p d every time.

Describe the solution you'd like

• Given I have a package definition in a folder
• When I run zarf dev test package/folder
• Then Zarf creates the package and deploys the package in one fell swoop without an intermediate tarball
• And When I run zarf dev test package/folder --force-yolo
• Then Zarf again creates and deploys the package but forces the package to be in YOLO mode and will not pull images/repos into the package (without the author needing to change the YOLO key in the definition)

Describe alternatives you've considered

We could add a flag on deploy or create but having them combines allows for tweaks to happen faster with fewer disk writes in between runs.

Additional context

This command will allow us to add testing specific flags and features for Zarf packages, and as a part of this change we should remove the dev alias from internal and instead make prepare an alias of dev so that "developing Zarf packages" is the primary wording going forward for the package definition writing process.