apr(wiring): resolve apr-repo-transfer against the corrected customer-owned creation model

[JSONbored]

Problem

apr-repo-transfer.ts (377 lines) plus apr-repo-binding.ts's transfer-authorization
reasoning assume a repo created under a loopover-controlled org that later moves to the
customer. apr-repo-creation.ts creates it under the customer's account from the start.
If creation is customer-owned, there is nothing to transfer and the path is vestigial.

Scope

• Confirm whether any intended flow still needs transfer (e.g. a customer without a GitHub
  account at submission time, or a repo started internally then handed over). If none does,
  the path is dead
• If dead: remove apr-repo-transfer.ts, its route, and its tests; keep
  apr-repo-binding.ts if the binding is still needed for tenant authorization generally
  (it is — see apr(completion): persist completion and repo-binding records (#7664, #9490) #10084) and rewrite its header so its rationale no longer rests on transfer
• If a real flow needs it: correct the stale header in apr-repo-transfer.ts and document
  which creation path leads to it, so both models are deliberate rather than accidental
• Either way, Implement APR repo-transfer-to-customer initiation via GitHub's transfer API #7638 and Decide policy for when an APR repo-transfer offer is surfaced to a customer (deferred from #7638) #7742 need their status updated to match the outcome

Acceptance

The tree carries exactly one repo-ownership model. No file's header describes a design that
is no longer in force.

[linear-code]

JSO-7086