controller: Separate instance_client

[ggevay]

This is a refactoring related to the frontend peek sequencing, partially addressing the second paragraph of #33713 (comment) + other related discussions with Moritz and Jan.

This PR is purely code movement: it moves the Client from instance.rs into a new file instance_client.rs, and renames it to InstanceClient. (This is used by the frontend peek sequencing directly, bypassing the ComputeController, because we don't want the Coordinator to be a bottleneck for fast-path peeks.)

Part 1 of 3 from the original #34839. (Based on @teskje's comment there, we probably do want this code movement, right? What do you think, @antiguru?)

[github-actions]

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

[teskje]

LGTM, just a couple nits.

[ggevay]

Thank you, all done.

(Will wait for @antiguru's review before merging.)

[antiguru]

Looks fine, thanks