Resolve Parent Values early when their elements are children

If you query the categories of a game and query `category.Game` afterwards, there doesn't need to be a request anymore, as that is already known. The Caching algorithm might not catch that, as the game might've not been queried by it's ID initially, so the URL is different.
- [x] Game -> Category -> Game
- [x] Series -> Game -> Series
- [x] Category -> Record -> Category
- [x] Category -> Record -> Game
- [x] Game -> Record -> Game
- [x] Game -> Record -> Category
- [ ] User -> Runs -> User
- [ ] User -> Records -> User

Probably even more

Start by tracing the caching algorithm and how related API resources are resolved after queries. Use the checked relationship chains as initial cases, then verify that querying a parent after its child requires no additional request; the remaining User relationships are also listed as unfinished scope.

Written by the indexing model from the issue text.