Scale back the code.

[spacedmonkey]

Context

While reviewing #12197, I discovery that that data needed for this functionality is already in the REST API. As it is hard to point developers in the right direction, here is an example of how this functionality could work.

Summary

Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

• This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

Reviews

Does this PR have a security-related impact?

Does this PR change what data or activity we track or use?

Does this PR have a legal-related impact?

Checklist

• This PR addresses an existing issue and I have linked this PR to it in ZenHub
• I have tested this code to the best of my abilities
• I have verified accessibility to the best of my abilities (docs)
• I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
• This code is covered by automated tests (unit, integration, and/or e2e) to verify it works as intended (docs)
• I have added documentation where necessary
• I have added a matching Type: XYZ label to the PR

---

Fixes #

[timarney]

Commits cherry picked into #12197 (comment)