Optimize fetch_repository resolver

[Swatinem]

Previously, the owner.repository resolver would unconditionally execute a very complicated query through fetch_repository.

We can avoid that expensive subquery by inspecting the requested fields as stated in the graphql query.

---

This might fix codecov/engineering-team#3396

[seer-by-sentry]

✅ Sentry found no issues in your recent changes ✅

[codecov]

Codecov Report

Attention: Patch coverage is 92.10526% with 3 lines in your changes missing coverage. Please review.

Project coverage is 96.32%. Comparing base (1983799) to head (1649d07).
Report is 2 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
graphql_api/helpers/requested_fields.py	88.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1261      +/-   ##
==========================================
- Coverage   96.33%   96.32%   -0.02%     
==========================================
  Files         492      493       +1     
  Lines       16898    16933      +35     
==========================================
+ Hits        16278    16310      +32     
- Misses        620      623       +3     

Flag	Coverage Δ
unit	96.32% <92.10%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[codecov-notifications]

Codecov Report

Attention: Patch coverage is 92.10526% with 3 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
graphql_api/helpers/requested_fields.py	88.00%	3 Missing ⚠️

📢 Thoughts on this report? Let us know!

[joseph-sentry]

i would just leave a comment in the requested_fields.py to look at graphql/language/parser.py to understand what's going on there

[sentry]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ OperationalError: server closed the connection unexpectedly /graphql/{service} View Issue
• ‼️ GraphQLError: server closed the connection unexpectedly /graphql/{service} View Issue

_{Did you find this useful? React with a 👍 or 👎}