feat(deploy)!: introduce connected mode

[AustinAbro321]

Description

This introduces a connected mode, allowing users to deploy to packages created with images and git repos, without actually pushing those images or git repos or mutating resources to point to Zarf infrastructure. This should let users have a single zarf.yaml that works in both connected and disconnected environments.

This doesn't introduce "connected" packages would wouldn't include images and git repos, however I think this can be a future enhancement.

This replaces the zarf dev deploy --no-yolo flag with --connected=false (connected defaults to true in dev deploy mode). I bit awkward for a boolean flag, but I prefer the consistency

The breaking change here is that yolo mode and dev mode now by default label resources to not be mutated by the agent. I can't think of a strong case for this use case, as the only behavior of yolo mode previously was that it could deploy resources without Zarf existing, and yolo mode packages cannot have images or repos.

Something to note that's stayed consistent with yolo mode is that connected deploys set values for the Zarf state struct, and pass state through the application, but they don't persist any state to the cluster.

Related Issue

Fixes #4580

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	d3bc845
🔍 Latest deploy log	https://app.netlify.com/projects/zarf-docs/deploys/69dd5043c8b10200094b4920

[codecov]

Codecov Report

❌ Patch coverage is 22.72727% with 85 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/internal/packager/helm/post-render.go	34.00%	31 Missing and 2 partials ⚠️
src/pkg/packager/deploy.go	0.00%	27 Missing ⚠️
src/pkg/state/state.go	0.00%	16 Missing ⚠️
src/cmd/package.go	33.33%	4 Missing ⚠️
src/internal/packager/helm/chart.go	0.00%	2 Missing ⚠️
src/pkg/packager/pull.go	0.00%	1 Missing and 1 partial ⚠️
src/cmd/dev.go	66.66%	1 Missing ⚠️

Files with missing lines	Coverage Δ
src/cmd/viper.go	55.91% <100.00%> (+1.46%)	⬆️
src/cmd/zarf_tools.go	32.80% <ø> (+0.06%)	⬆️
src/pkg/packager/dev.go	0.00% <ø> (ø)
src/pkg/packager/load.go	62.89% <100.00%> (-0.75%)	⬇️
src/cmd/dev.go	45.80% <66.66%> (+0.15%)	⬆️
src/internal/packager/helm/chart.go	1.16% <0.00%> (ø)
src/pkg/packager/pull.go	50.00% <0.00%> (+2.94%)	⬆️
src/cmd/package.go	38.12% <33.33%> (+0.02%)	⬆️
src/pkg/state/state.go	25.37% <0.00%> (-1.62%)	⬇️
src/pkg/packager/deploy.go	0.00% <0.00%> (ø)
... and 1 more

... and 8 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[soltysh]

One comment regarding testing, otherwise this lgtm

[brandtkeller]

lgtm - the issue outlines some interesting constraints we'll want to keep an eye on regarding "Connected Package creation/pull".