Add package 'alchemy-config' into the RHAI pipeline onboarding collection.

The package requires builder repository onboarding before it can be added to the RHAI pipeline. This ticket is blocked by the builder onboarding ticket.

Summary

Here is the executive summary formatted as a JIRA comment in JIRA wiki markup:

Executive Summary: alchemy-config Package Analysis

alchemy-config is a pure Python package providing YAML-based configuration management with environment variable overrides. It is a direct dependency of caikit (>=1.1.1,<2.0.0) and has been assessed as Simple complexity (1/10) with no blockers for Red Hat onboarding. The entire package consists of only ~400 lines of Python across two source files, requires no native compilation, and produces a universal py3-none-any wheel. Version 1.1.3 (latest, released 2024-01-30) is the appropriate target. The package is MIT-licensed, fully compatible with Red Hat distribution requirements.

The build process is straightforward with one notable quirk: setup.py requires the RELEASE_VERSION environment variable to be set at build time, or the build will fail with an AssertionError. For RPM packaging, this is resolved by setting RELEASE_VERSION=%{version} in the %build section. The sole runtime dependency is PyYAML (>=5.3.1), which is already available in RHEL as python3-pyyaml. There are no C extensions, no system library dependencies, and no platform constraints. The recommended build command is:

export RELEASE_VERSION=1.1.3
python setup.py sdist bdist_wheel

The package has a solid test suite (28 tests, 98% coverage, all passing) and no critical open issues. The only open GitHub issues are a feature request for list support in environment variable overrides (#2) and the RELEASE_VERSION build quirk (#9), both with known workarounds. Note: the package uses legacy setup.py without pyproject.toml, which emits deprecation warnings but builds successfully with modern tooling. The dependency chain is minimal (caikit -> alchemy-config -> PyYAML), the codebase is stable, and the risk of breaking changes is low. Target delivery for AIPCC-10922 by 2026-03-18 is entirely feasible given the simplicity of this package.