pageserver: rename control plane client & chunk validation requests

[jcsp]

Problem

• In storage controller: read from database in validate API #8784, the validate controller API is modified to check generations directly in the database. It batches tenants into separate queries to avoid generating a huge statement, but
• While updating this, I realized that "control_plane_client" is a kind of confusing name for the client code now that it primarily talks to the storage controller (the case of talking to the control plane will go away in a few months).

Summary of changes

• Big rename to "ControllerUpcallClient" -- this reflects the storage controller's api naming, where the paths used by the pageserver are in /upcall/
• When sending validate requests, break them up into chunks so that we avoid possible edge cases of generating any HTTP requests that require database I/O across many thousands of tenants.

This PR mixes a functional change with a refactor, but the commits are cleanly separated -- only the last commit is a functional change.

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.
• Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
• If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

• Do not forget to reformat commit message to not include the above checklist

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[github-actions]

4968 tests run: 4804 passed, 0 failed, 164 skipped (full report)

---

Flaky tests (3)

Postgres 17

• test_pageserver_compaction_smoke: release-arm64
• test_ondemand_wal_download_in_replication_slot_funcs: release-arm64

Postgres 14

• test_scrubber_physical_gc[4]: release-arm64

Code coverage* (full report)

• functions: 31.8% (7415 of 23293 functions)
• lines: 49.9% (59566 of 119383 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
753d868 at 2024-09-13T10:41:10.857Z :recycle:}