[PAR Phase 4] Improve project discovery with strong project quality signals(automated) and incentivize peer code review(manual)

Branching this issue off of: #2666584: [Community Initiative Proposal] Project Applications Process Revamp as the primary meta issue is becoming unwieldy.

With the gates open to new users creating projects on Drupal.org without going through a project application process, code quality, peer review, and project discovery is more important than ever.

We can take some guidance on what signals are important based on the PAReview template.

There are several categories of improvements we'd like to make in this area:

[Please note that not all of these issues will necessary be included in our implementation plan for this phase.]

Code/project quality signals

• Port features of the PAReview.sh script to DrupalCI, and surface the results on Project pages
• Integrate static analysis tools and surface this on Project pages, e.g:
  • #2809373: Support for Code Climate
  • #2844865: Review Coverity scan for Drupal core one time
• Provide code coverage metrics on project pages
• #1134450: Automatically degrade maintenance and development status of projects over time
• Consider presenting usage data as a 'percentile of sites use this module' i.e: 20% of sites use this module
• Consider surfacing data about past security issues with the project and the maintainers responsiveness
• Consider including how many times the project was featured in a case study
• #2847391: Add project categorization to indicate the module / theme passes accessibility standards
• #2186377: Highlight projects that follow Best Practices

Discourage duplicate effort

• This is the sort of thing that can sometimes be accomplished by simply allowing ratings and other factors (^^ such as the above) to separate the best of the implementations from the duplicates
• #937778: Similar Module Comparison
• Use Flag to 'report duplicate module' (who would be alerted? both maintainers?)

Incentives for peer review

• #2850494: Plan the process for incentivizing code review after project apps revamp

Ratings & Reviews

• As an MVP - consider allowing users to 'star' or 'favorite' projects using Flag module
  • #1973934: Allow users to "Star"/"Bookmark"/"Like" their "Favorites" on Drupal.org
  • #50605: Add user ratings for projects
  • #2192181: Allow users to review and vote on various aspects of projects.

Project discovery

• Do a design pass on project pages to coordinate how all these project quality signals are presented to end users
• Factor these project quality signals into search ranking
• #2659570: Add a filter on project browsing pages for release status (e.g. dev, alpha, beta, rc, prod)
• #2213211: Better Module/Theme Listing Pages
• #1434450: Add the ability to follow projects like we follow issues