The workspace-init component deploy fan-out is retired

[sameera]

As a lead initialising a workspace, I want that step to stop deploying components into member repositories, so that it does not recreate the per-repository copies this refactor exists to remove.

Acceptance Criteria

• Given the workspace initialisation path, when it runs, then it deploys no components into any repository.
• Given that path's output and prompt text, when they are read, then neither offers nor describes a component deploy.
• Given a lead initialises a workspace after this story, when they follow the output, then they are told that components come from the install location and are not deployed per repository.
• Given the rest of the workspace initialisation behaviour, when it runs, then it is unchanged — only the component fan-out is removed.

Notes

This is a live code path, not dead code: the workspace-init verb currently fans deployComponents out across member repositories. Under replacement it has nothing to deploy.

It was carried inside the migration story as a seventh criterion, which made that story two deliverables and put a behaviour change affecting every workspace-init user inside a story about migrating one repository. It is separated here.