Packager Refactor - Parent Issue

[brandtkeller]

Describe what should be investigated or refactored

As part of schema work it has been identified that src/packager intertwines "deploy time" and "package create time" logic.

We will begin by refactoring the following pieces of src/packager into src/packager2 - this will allow us to re-implement this functionality without making breaking changes to Zarf in between releases. We will then swap over the calls to packager.() functions to packager2.() and deprecate src/packager functionality for src/packager2 (while renaming packager2 to packager)

Decisions Made:

• To refactor "Opts" out of the larger Packager struct, Opts will be moved into their respective "primary file". All exported functions will take its "related" Opts struct as a function argument.
  • E.g. - InspectOpts is moved into the inspect.go file within packager2

Links to any relevant code

Additional context

Doing this work should consider the following targets:

• Better unit testing
• Less global state
• Less side effects from calls such as os.Chdir
• Cleaner API for library users
• Support for standard cross-architecture workflows

[brandtkeller]

See #2969 for historical reference