feat: package generation ALPHA

[andrewg-xyz]

Description

Introduce Zarf package generation from a source

Related Issue

Fixes #821

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	c2d07d0
🔍 Latest deploy log	https://app.netlify.com/sites/zarf-docs/deploys/65f1a807690aa20008adc30f

[andrewg-xyz]

I was able to smoke test function pre and post rebase via:

mkdir tmp-gen && cd tmp-gen
helm pull oci://ghcr.io/stefanprodan/charts/podinfo && tar -xf podinfo-6.5.4.tgz
../build/zarf-mac-apple package generate my-podinfo --from ./podinfo

Both produced zarf.yaml

kind: ZarfPackageConfig
metadata:
  name: my-podinfo
components:
- name: component-local-chart-podinfo-87f03f37-b831-4968-8b5b-acf0a54530b6
  charts:
  - name: podinfo
    version: 6.5.4
    localPath: ./podinfo
    namespace: zarf-generated-local-chart-podinfo

[andrewg-xyz]

a few things to chase down/confirm:

• ZarfCreateOptions.{CachePath,Insecure} moved to ZarfCommonOptions.{CachePath,Insecure}
• ZarfCreateOptions.OutputDirectory >> move to? maybe ZarfPullOptions.OutputDirectory
• a few merge conflicts were due to functionality partially ported to pkg, need to confirm no more internal functionality exists that has been moved

a few things I know can be improved:

• switch blocks in package Generate command
• check implementation for new package structure in zarf

[AustinAbro321]

LGTM, we will need approval from someone else on the zarf team

[Racer159]

Adding comments, mostly cleaning up string building, but there are a few things that could make this more generally useful and one issue with garbled text.