N+1 issue when loading list of projects (Follow-up from "Resolve "Redesign project lists UI"")

When loading the project list locally on http://localhost:3000/ there's an N+1 issue:

GitalyClient#call called 36 times from single request. Potential n+1?
The following call site called into Gitaly 16 times:
lib/gitlab/gitaly_client.rb:120:in `call'
lib/gitlab/gitaly_client/commit_service.rb:446:in `call_find_commit'
lib/gitlab/gitaly_client/commit_service.rb:275:in `find_commit'
lib/gitlab/git/commit.rb:66:in `block in find'
lib/gitlab/git/wraps_gitaly_errors.rb:7:in `wrapped_gitaly_errors'
lib/gitlab/git/commit.rb:65:in `find'
app/models/repository.rb:1056:in `find_commit'
app/models/repository.rb:109:in `commit'
app/models/project.rb:636:in `commit'
lib/gitlab/cache/ci/project_pipeline_status.rb:118:in `block in commit'
lib/gitlab/utils/strong_memoize.rb:28:in `strong_memoize'
lib/gitlab/cache/ci/project_pipeline_status.rb:117:in `commit'
lib/gitlab/cache/ci/project_pipeline_status.rb:52:in `load_status'
lib/gitlab/cache/ci/project_pipeline_status.rb:23:in `block in load_in_batch_for_projects'
lib/gitlab/cache/ci/project_pipeline_status.rb:21:in `load_in_batch_for_projects'
app/helpers/projects_helper.rb:192:in `load_pipeline_status'
app/views/shared/projects/_list.html.haml:15:in `_app_views_shared_projects__list_html_haml___3592720212301275510_70249406004300'
app/views/dashboard/projects/_projects.html.haml:1:in `_app_views_dashboard_projects__projects_html_haml___2135125151576847022_70249289550440'
app/views/dashboard/projects/index.html.haml:15:in `_app_views_dashboard_projects_index_html_haml___723817947304561004_70249299922880'
app/controllers/application_controller.rb:116:in `render'
app/controllers/application_controller.rb:420:in `set_locale'
lib/gitlab/query_limiting/middleware.rb:17:in `block in call'
lib/gitlab/query_limiting/transaction.rb:39:in `run'
lib/gitlab/query_limiting/middleware.rb:16:in `call'
lib/gitlab/correlation_id.rb:15:in `use_id'
lib/gitlab/webpack/dev_server_middleware.rb:27:in `perform_request'

The following discussion from !22682 (merged) should be addressed:

Edited by Martin Wortschack