ZEP-0039: Enhance Yolo Experience

[brcourt]

• One-line PR description: adding new ZEP

• Issue link: Enhanced Yolo Experience #43

• Other comments:

[AustinAbro321]

This is great user feedback and I am excited to see where this goes. I believe the use case of wanting to maintain packages for both a connected and disconnected environment is relatively common among community members and I think it aligns well with our project direction and intent. YOLO packages right now allow connected deployments without having to initialize Zarf state, but the UX of maintaining packages for both is not good.

The problem here is well defined, but I think there are several ways a solution could go. I plan to spend some time ideating on this as well. I encourage you to add your ideas from #4139 to your proposal. Feel free to add multiple sections in the proposal with different ideas as we workshop this.

Note that we plan to introduce a new schema version at some point, ideally in the next six months or so but timelines are tentative (#3433). This makes it much easier to make a breaking change around the current .metadata.yolo key.

P.S. I agree the name YOLO should change, but yeah we can handle it in another proposal. It'll at least be handled in #3433