Add Runtime to an Approved Registry (Iron Bank?)

[adam-defenseunicorns]

Is your feature request related to a problem? Please describe

As a Delivery engineer when I add a new service (Runtime) to a mission env it is much more difficult to get that package approved if it is not included in an Approved Registry.

Anything tool or service running persistently in staging or prod will come from an approved registry (Gabe)

Describe the solution you'd like

More info needed

• Given a new (persistent) tool or service is added to UDS Core like Runtime
• When that service is expected in delivery staging and prod environments
• Then that tool/service should be added to an approved registry

Describe alternatives you've considered

• Use Lula to generate the body of evidence needed to satisfy any concerns that an ISSM/ISSO/AO may have

Additional context

• Follow on ask is to have a playbook for adding a new tool/service to Ironbank or another approved registry with any lessons learned and tips/tricks.

[adam-defenseunicorns]

Current mitigation is to make Runtime optional in core, but included with the demo bundle.