`akmods` Module: Accept `ogc` as a valid string for `base` enum

[lotsospaghetti]

Bazzite now uses the OGC kernel instead of its own bespoke one, and as such the Universal Blue akmod images now use tags named ogc-<fedora_version> for kernel modules built for Bazzite. I figured this out after I attempted to use the akmods module to add ZFS to my Bazzite DX-based image on a whim which produced the following error:

ERROR: failed to build: failed to solve: ghcr.io/ublue-os/akmods:bazzite-43: failed to resolve source metadata for ghcr.io/ublue-os/akmods:bazzite-43: ghcr.io/ublue-os/akmods:bazzite-43: not found

Out of curiosity I ran another build that replaced bazzite with ogc and some part of the BlueBuild parser predictably didn't like that:

× Recipe ./recipes/recipe.yml failed to validate
  ╰─▶   × 1 error encountered
          ╭─[./recipes/recipe.yml:11:11]
        8 │ 
        9 │ modules:
       10 │   - type: akmods
       11 │     base: ogc
          ·           ─┬─
          ·            ╰── value is not valid under any of the schemas listed in the 'anyOf' keyword
       12 │     install:
       13 │       - zfs
       14 │ 
          ╰────

I'm not sure whether the akmods module is supposed to pull some wizardry to make ZFS-on-Bazzite work or if my particular scenario was doomed to fail from the start, but for akmods that are actually built for Bazzite BlueBuild should accept ogc as a valid string here.

[xynydev]

I fixed the schema issue now, you can report back if it works. Note that it takes a moment for the schemas to update so don't be impatient.

Also, no, we do not have any wizardry. The module just installs the akmods. ZFS installation is currently broken also: #565