feat: publish initial infrastructure kit collection

[Brad-Edwards]

Summary

• publish all 38 infrastructure kits required by feat(kits): publish reusable kits for proven environment infrastructure env-packs#190 as independently versioned RAES modules
• give every kit a domain-specific parameter, declared infrastructure surfaces, meaningful benign seed inventory, and pack-local integration guidance
• bind each release's exact files with a RAES associated-artifact manifest and declare component-inventory inputs at RAES source granularity
• document and enforce a catalog-wide content strategy across eight broadly useful infrastructure concerns
• validate every release under default and materially different parameters plus a representative multi-kit composition

Scope

The catalog contains static environment infrastructure only. It adds no backend code, runtime API, scenario behavior, compatibility verdict, SBOM format, or realization claim.

Verification

• python -m unittest discover -s tests
• python tests_integration/kit_author_walkthrough.py --catalog <catalog> from the companion env-packs branch (25 passed)

Depends on the kit contracts and CLI in OpenRAE/env-packs#190.

[doublewhy]

Closing this draft as a duplicate copy of content already shipped by OpenRAE/env-packs, not as a decision against a future explicit catalog-authority transfer.

Verification at the current heads:

• This PR: bb6fec1dbeb012fad6be4104b430c3b7b3b7fc3d
• Released env-packs v4.0.1 commit: d9469706066ee527ab7f7b49e786fa608227f5b6
• Both repositories' kits/ path resolves to the same Git tree object: 09ff9f4f6c24de37e10164344310d43b7d46dc3a
• Each tree contains the same 38 top-level kit directories and 266 files; a recursive comparison found no differing kit file.
• The env-packs content is in the published v4.0.1 release, including its released wheel/sdist and attestations.

Merging this PR while the same bytes remain shipped and editable in env-packs would create two authorities without an ownership migration. If the kits move later, that should be an explicit one-way transfer: pin source provenance, define release/compatibility ownership, remove or freeze the originating editable copies, and verify consumers against the new released authority. This copy-only draft does not perform that transfer, and naming/publication work is currently held.