Support last_repository_check_failed parameter on Projects GraphQL API

What does this MR do and why?

First step needed to fix the regression reported in "last_repository_check_failed" filter does not ... (#567350 - closed)

• Support last_repository_check_failed parameter on Projects GraphQL API
• Add last_repository_check_failed search filter on the new Admin Area > Projects

Additional context:

There's a section in our documentation that suggests readers to visit the /admin/projects?last_repository_check_failed=1 to check for projects with failed repository checks.

We overlooked this feature during the migration to Vue because it was not normally accessible through the UI.

Query Plans

last_repository_check_failed=true

https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43085/commands/131709

last_repository_check_failed=false

https://console.postgres.ai/gitlab/gitlab-production-main/sessions/43085/commands/131708

References

• Related to #567350 (closed)
• Closes #567647 (closed)

Screenshots or screen recordings

last_repository_check_failed=true

last_repository_check_failed=false

How to set up and validate locally

1. Run Project.find(...).update!(last_repository_check_failed: true) in the rails console.
2. Go to /-/graphql-explorer and run the following query

{
  projects(lastRepositoryCheckFailed: true) {
    nodes {
      id
      name
    }
  }
}

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.