feat: Create Recipe V2 schema

[gmpinder]

This PR adds the schema for Recipe V2 (a long time coming). This is based on the discussion in blue-build/cli#180.

Example:

version: 2
base:
  image:
    registry: ghcr.io
    repository: blue-build/base-images/fedora-base
    tag: 44
  # image: ghcr.io/blue-build/base-images/fedora-base:44 # Can  be defined as a string too
  public-key: https://raw.githubusercontent.com/blue-build/base-images/refs/heads/main/cosign.pub
metadata:
  name: test
  description: Test for recipe v2
  labels:
    'org.bluebuild.test': test value
spec:
  tags:
    - test
  platforms:
    - linux/amd64
    - linux/arm64
  tool-versions:
    bluebuild: main
modules:
# ....

[cloudflare-workers-and-pages]

Deploying bluebuild-schema with    Cloudflare Pages

Latest commit:	2ff2725
Status:	✅  Deploy successful!
Preview URL:	https://b65f6d71.schema-e29.pages.dev
Branch Preview URL:	https://recipe-v2.schema-e29.pages.dev

View logs

[xynydev]

Seems great. I like that image can be both a string and an object. I would definitely recommend using the string for most humans, but for changing programmatically this is great!

The distinction between metadata and spec might be a bit confusing. For example, why are labels metadata but tags spec? Well, of course this is because tags are used to pull the image, and labels are just metadata. This is not a problem with the schema then I guess, just something that needs to be documented. And you have documented it. I'm just thinking out loud forgive me...

[xynydev]

Approved!!!!! 🎉

[gmpinder]

The distinction between metadata and spec might be a bit confusing. For example, why are labels metadata but tags spec? Well, of course this is because tags are used to pull the image, and labels are just metadata. This is not a problem with the schema then I guess, just something that needs to be documented. And you have documented it. I'm just thinking out loud forgive me...

I was kind of going back and forth about the tags being under spec versus metadata. The way I see it is that metadata is just information about the image and spec contains options for how to build the image. The tags themselves are kind of part of the build, but they don't really affect how the internal parts of the image are built, so I could go either way on that front.