Creation of a slim init package

[brandtkeller]

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

The current Init package requires ~340M space. This includes k3s as well as the other required and optional components for many of zarfs features.

As it stands - that included k3s capability does provide value - but we also see many environments which are using zarf with managed or more highly-available clusters. In these cases - removing the k3s component from the init package can slim the init package down to ~140M.

Describe the behavior you'd like

• Given required configuration for mutliple init packages
• When a release occurs
• Then an init and slim init package are released

Describe alternatives you've considered

Continue to write documentation to support customizing init packages

Additional context

Doing this should straightforward with composability.