Currently, we generate manifests in the hosted process using the follow process:

1. The composer container initializes a manifest. That mostly means collecting all items that has to depsolved, or resolved (ostree commits, containers).
2. This list is sent to a worker that does the actual depsolving and resolving.
3. The depsolved result is sent back to composer where it's joined with the initialized manifest and a final manifest is produced.
4. The final manifest is then used for the actual image build.

However, otk does steps 1-3 in one call, so we have to adjust our architecture. We cannot depsolve in the composer container because it's not subscribed, nor it has access to the internal content needed for the internal tenant. Thus, we need rework the architecture to generate manifests fully on workers.

Goal:

• Implement a new manifest generation job that runs on a worker. This means running otk instead of relying on the internal definitions in images.
• Implement a switch that allows compose requests to use this new job instead of the current one.
• Flip the switch for CentOS Stream 9.

Acceptance Criteria:

• A compose in console.redhat.com is built from a manifest generated by otk.