Flaky behaviour getting statuses on gitlab.com

[javiertuya]

Getting statuses cause intermittent exceptions when accesing fields from the GraphQL response, eg. when accesing the repository field at the projects query. It seems that the graphql response does not always guarantees the structure of the node content. Note that this does not appear when querying an on-premises instance.

[javiertuya]

Protected gitlab adapters against null iterations in graphql node items. Still remaining:

• Intermittent faults when getting the labels for all projects due tu insufficient permissions (keep console log, but remove the error message in the ui)
• Sometimes, the ordering of branches adds older grups before today, this is apparently caused by empty dates of the branches without MRs, issue Missing attributes in a GitLab Merge Request without branch in pipelines #3, and will be fixed there.