Technical Investigation: Determine viable option for Issue #336199

In order to properly work on #336199 (closed) we need to determine which one of the suggested options is the right one to implement:

Options

1. Change this query to 2 queries to avoid the join (not sure if this will be possible yet as it depends on how this scope is used if you can avoid loading too many project IDs into memory)
2. Refactor/change the feature so that this query is not necessary
3. De-normalize data in some way so that you don't need to join

The option we choose must:

1. Not break the GraphQL functionality.
2. Implement reasonable query limits that offend a very small number of customers, if any.
3. Be considered in the context of parallel work on other teams, to ensure we're not reinventing solutions and adding maintenance cost.