Projects: Better projects fetching

[iLLiCiTiT]

Changelog Description

Heavily modified how projects are fetched in specific use cases and fixed few bugs related to it.

Additional review information

Added new method get_rest_projects_list which receives name, code active, createdAt and updatedAt data for all projects.

Modified _get_project_graphql_fields to return what fetch types has to be done to collect all requested data. GraphQl fetching supports more fields like bundle, data, usedTags, etc. Use both GraphQl and rest only if it is necessary. Added few safe guards for fetched data, e.g. "data" can be None and productTypes might not be in graphql project,

Testing notes:

1. Using get_projects(fields={"name", "active", "data"}) won't trigger get_rest_projects.
2. Using get_projects(fields={"name", "active", "data", "config"}) won't trigger _get_graphql_projects.
3. Using get_projects(fields={"name", "active", "data", "config", "productTypes"}) will trigger both get_rest_projects and _get_project_graphql_fields.

[kalisp]

Not completely sure how to test it, but did use debugger and all assumption in description are correct.
(Actually _get_project_graphql_fields is hit in second step, but it bails early (line 644), I guess that is correct behavior.)

[iLLiCiTiT]

There was a bug in testing descriptions _get_project_graphql_fields should be _get_graphql_projects.