[RHIDP-12668] Update Library Image to Sprint 3289 Version

[Jdubrick]

What does this PR do?:

• Updates the Lightspeed Core base image to the one we are using for Sprint 3289
• Updates all references to Llama Stack version to match the 0.5.2 present in the Lightspeed Core image
• Adds sync/validation functionality so we can keep the config files consistent based on the source of truth from https://github.com/redhat-ai-dev/lightspeed-configs/tree/main
• Disables old CI we don't use anymore (removes it)

Which issue(s) this PR fixes:

https://redhat.atlassian.net/browse/RHIDP-12668

PR acceptance criteria:

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened and linked to this PR, if they are not in the PR scope due to various constraints.

• Tested and Verified

• Documentation (READMEs, Product Docs, Blogs, Education Modules, etc.)

How to test changes / Special notes to the reviewer:

[maysunfaisal]

@Jdubrick why dont we promote the configs repo and just phase this repo out?

[Jdubrick]

@Jdubrick why dont we promote the configs repo and just phase this repo out?

@maysunfaisal @michael-valdron is onboarding the library side of the build to Konflux as a fallback plan for 1.10, incase we need it. There's been discussion about LCORE providing a library mode image however.

I think we keep it relatively updated for now but am totally good with phasing this repo out and archiving it if:

1. 1.10 comes and goes and we didn't need to fallback to library mode
2. LCORE provides a library mode image and makes this redundant

wdyt?

[michael-valdron]

@Jdubrick Would it make sense to pin these images? Considering renovate patching and release build consistency.

[gabemontero]

that would be consistent with what we see here for the lightspeed/lls/rag images ... +1

[Jdubrick]

To be honest, the env vars you listed here aren't really used in this repo, they're just a side effect of the sync for getting the envs for enabling inference/safety etc from redhat-ai-dev/lightspeed-configs.

I will open a PR to lightspeed-configs repo to pin the RAG_CONTENT_IMAGE and OLLAMA_IMAGE to a sha instead of a tag that could move, does that work? I'll then add a commit to this PR to pull those changes

[Jdubrick]

First PR: redhat-ai-dev/lightspeed-configs#8

[gabemontero]

I just approved that PR

[Jdubrick]

Pulled changes in via this commit: a5828d0

[Jdubrick]

Also, if we want to move to digests, I'm all for that. I would handle it in a different issue though

[michael-valdron]

/lgtm