Evaluate v1beta1 migration

[AustinAbro321]

Description

Using this to evalute the changes in zarf-dev/proposals#52. No intention to merge.

Seeing this in action points to a few holes:

• UDS core uses an import strategy wherein they point standard to base, then point to base to the relevant zarf.yaml files. It's probably not a huge lift to ask them to change this, but this system does reduce duplication in the event that folder names change.
• There is an implicit ordering in a zarf.yaml file, the first component in a list is installed, then the second and so forth. By asking users to break apart their zarf.yaml files into Zarf Component Config files, they may lose this implicit ordering, and it could be more confusing to determine the order of components. The istio example in this PR is a fair example.