chore: separate schema generation

[AustinAbro321]

Description

This moves schema generation to it's own folder rather than being a part of the Zarf binary. This moves the schema's to their own folder to help keep the repo clean as the number of schemas will grow as we introduce schema versions. However this does not delete the zarf.schema.json at the root of the repo as we've pointed users to that file in the docs to get schema validation in VS code.

This doesn't remove the invopop/jsonschema from the Zarf CLI, however there is only one place left it is used. Likely this can be removed in a future PR and replaced with runtime validation.

zarf/src/api/v1beta1/component.go

Line 318 in 8100c69

func (ZarfComponentImport) JSONSchemaExtend(schema *jsonschema.Schema) {

Relates to #2788

Checklist before merging

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines	Coverage Δ
src/cmd/internal.go	0.00% <ø> (ø)

[AustinAbro321]

I didn't build a replacement for this as I don't think it's needed. I'm not sure what the original use case was for adding this, though I don't think it makes sense to have an internal command generating a schema for types users shouldn't be creating.

[phillebaba]

Good jobs getting this done. A couple of comments.

Is the docs changes related to these changes or are we fixing this because we found out it was wrong during this work?

We wont remove any dependency in the Zarf CLI in this change. Just making sure because the description makes it seem like we are reducing the amount of dependencies.

The last thing is that I think this code should go in a tools directory located in the root of the project. It would be good if the shell script that goes along with it would also be located with the Go code instead of in the hack directory. Here is an example of how other projects solves this.
https://github.com/openshift/origin/tree/master/tools

I would like @schristoff input on this type of project structure.

[AustinAbro321]

Is the docs changes related to these changes or are we fixing this because we found out it was wrong during this work?

It's related to this work. Essentially we're copying the alpha schema to a different folder. I'm not deleting the original zarf.schema.json since many users rely on it. However once we're in v1 and users no longer need that original zarf.schema.json I'm thinking we can move all the schemas to the tools folder

We wont remove any dependency in the Zarf CLI in this change. Just making sure because the description makes it seem like we are reducing the amount of dependencies.

Yeah my description was confusing, fixed it.

The last thing is that I think this code should go in a tools directory located in the root of the project. It would be good if the shell script that goes along with it would also be located with the Go code instead of in the hack directory. Here is an example of how other projects solves this.

I would agree

[netlify]

✅ Deploy Preview for zarf-docs ready!

Name	Link
🔨 Latest commit	fd0ed8c
🔍 Latest deploy log	https://app.netlify.com/sites/zarf-docs/deploys/66d722b44fe90500075d6c1d
😎 Deploy Preview	https://deploy-preview-2886--zarf-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.