storage controller: use 'lazy' mode for location_config

[jcsp]

Problem

If large numbers of shards are attached to a pageserver concurrently, for example after another node fails, it can cause excessive I/O queue depths due to all the newly attached shards trying to calculate logical sizes concurrently.

#6907 added the lazy flag to handle this.

Summary of changes

• Use lazy=true from all /location_config calls in the storage controller Reconciler.

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

[github-actions]

2490 tests run: 2367 passed, 0 failed, 123 skipped (full report)

---

Flaky tests (1)

Postgres 14

• test_delete_tenant_exercise_crash_safety_failpoints[real_s3-tenant-delete-before-create-remote-mark-False-Check.RETRY_WITH_RESTART]: debug

Code coverage* (full report)

• functions: 28.8% (6981 of 24255 functions)
• lines: 47.3% (42876 of 90553 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
d5a694f at 2024-03-06T10:47:23.455Z :recycle:}

[koivunej]

Without the live migration lazy=true issue this is looking fine.