feat(api)!: initial integration of registry1 api flavor

[justinthelaw]

OVERVIEW

Adds the Registry1 flavor of the LeapfrogAI API to the developer workflow and increases Helm chart and Dockerfile standard (foreshadowing upcoming Helm and Dockerfile linting PR).

Once all other registry1 flavored images are published to IronBank, the e2e-registry1-weekly.yaml will need to have access to a uds-bundle.yaml that points to packages created using the registry1.dso.mil container registry. For now, as each component comes online, we can use the yq commands to temporarily modify each one within the workflow:

uds zarf tools yq -i '.packages[1] |= del(.repository)' uds-bundles/latest/cpu/uds-bundle.yaml
uds zarf tools yq -i '.packages[1] |= .ref = "registry1"' uds-bundles/latest/cpu/uds-bundle.yaml
uds zarf tools yq -i '.packages[1] |= .path = "../../../packages/api"' uds-bundles/latest/cpu/uds-bundle.yaml
uds zarf tools yq -i '.metadata.version = "registry1"' uds-bundles/latest/cpu/uds-bundle.yaml

BREAKING CHANGES

• LeapfrogAI API internal cluster service subdomain, and zarf-connect name, is now leapfrogai-api instead of api, following the convention of using the Helm chart name for template helpers
• LeapfrogAI API Zarf package now uses Zarf package template variable IMAGE_VERSION instead of LEAPFROGAI_IMAGE_VERSION, to align the build process with all other components/packages

CHANGES

• Adds FLAVOR flag to the Makefile, defaulting to upstream
• Adds registry1 Zarf package flavoring for the API
• Refactors manifest structure to align with UDS Common and Core best practices
• Slight optimizations to the LeapfrogAI API Dockerfile
• Implements and uses helper functions for Helm chart templating
• Adds documentation to mention and use the Registry1 flavor
• Adds weekly test for registry1 flavored API (to be refactored later on)
• Fixes UDS setup action usage and version, v0.14.0

[netlify]

✅ Deploy Preview for leapfrogai-docs canceled.

Name	Link
🔨 Latest commit	8a41f46
🔍 Latest deploy log	https://app.netlify.com/sites/leapfrogai-docs/deploys/66d76f9217bc7c00083a4a24

[justinthelaw]

Depends on documentation updates from #902, and then one more update on top of that documentation.

[justinthelaw]

Pending @YrrepNoj approval too! Thanks @gphorvath and @CollectiveUnicorn

[YrrepNoj]

One small change request and one pondering on if we should consider this PR a 'breaking' change.

[YrrepNoj]

LGTM. Thanks for the updates.