Provide separate project browsing views from project_release with release-aware features

Splitting this off from #357925: Provide default project browsing views that don't depend on project_release and #76726: Refactor project module to use Views [meta issue] so we have a more focused place to work on this specific task...

Although #357925 is going to clean up the default project browsing view(s) to not depend on project_release data, we still want project_release to provide its own default project browsing view(s) to make use of the release data and provide important release-specific features. The idea is that 'project_overview' (or whatever it's called) would be enabled by default, and 'project_release_project_overview' would be disabled by default, but there'd be a little section in project_release's INSTALL.txt that said something like:

If you want to use the more fancy project browsing view provided by project_release, be sure to disable the 'project_overview' view, and enable the 'project_release_project_overview' view instead.

project_release_project_overview would make good use of the following:
#539676: Expose {project_release_supported_versions} data to views
#539282: Denormalize release info a bit and store latest and recommended releases in {project_release_supported_versions}

to provide features like:

A) Filter projects based on releases for a given API term

B) Sort projects based on latest releases, latest releases per API term, etc.

C) Display latest + recommended release data in the project summaries (either directly as in the sample view I originally posted at #539682-4: Replace hard-coded release download table with a view, or by the somewhat treacherous approach of exposing the entire download table as a view field).

There might be more, but this is a pretty good start...