fix performance issues on /api/foods

[fleshgolem]

What type of PR is this?

• bug

What this PR does / why we need it:

As mentioned in discord, the /api/foods endpoint can be pretty slow if you have a larger number of foods and especially if you use the extras feature for foods. I identified two causes for this:

1. Any repository that just uses RepositoryGeneric's page_all functionality without modifications can not make use of eager-loading and if there are relations used in the response (i.e. label and extras in this case), they will all be lazy-loaded for any given entry
2. IngredientFood's getter_dict override was kinda terrible, because the line **GetterDict(name_orm) would cause pydantic to try and resolve ALL model relationships, even if they are not used in the response, causing even more lazy-loading

To improve on this, I added a query_options function to RepositoryGeneric, so every sub-repository can specify its own loading options, if needed. Additionally I rewrote the getter_dict override so it just does the thing it is supposed to do and not cause any more unnecessary loading

Which issue(s) this PR fixes:

No issue filed

Testing

Ran all the tests and tried everything manually

Release Notes

* Improve performance for loading foods on search page

[hay-kot]

To improve on this, I added a query_options function to RepositoryGeneric, so every sub-repository can specify its own loading options, if needed.

Very slick. Love this!