Cargo.toml: enable sso for aws-config

[erikgrinaker]

Problem

The S3 tests couldn't use SSO authentication for local tests against S3.

Summary of changes

Enable the sso feature of aws-config. Also run cargo hakari generate which made some updates to workspace_hack.

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

[arpad-m]

Ah that's maybe fallout from #9233 . We want SSO support everywhere, also for usage with the pageserver. Also, we want features to be uniqua over all combinations of crates (that's why we use workspace hack). So it would make sense to not add it to dev-dependencies but to the entry in dependencies.

[arpad-m]

(also, you might need to run cargo hakari generate, it's tested in CI)

[erikgrinaker]

Got it, thanks. I moved it into the root Cargo.toml, removed another explicit override in storage_scrubber, and reran cargo hakari generate. PTAL.

[github-actions]

5058 tests run: 4872 passed, 0 failed, 186 skipped (full report)

---

Flaky tests (3)

Postgres 17

• test_subscriber_restart: release-x86-64

Postgres 16

• test_subscriber_restart: release-x86-64

Postgres 14

• test_ondemand_wal_download_in_replication_slot_funcs: release-x86-64

Code coverage* (full report)

• functions: 31.3% (7488 of 23897 functions)
• lines: 49.5% (60127 of 121377 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
568bbed at 2024-10-04T09:27:57.064Z :recycle:}