Move the GIT Info Report to its own page

We could also make it a local tab of the Status Report.

Easiest and probably also best (most straightforward) is to strip down gitinfo.install. We add also $phase === 'install' so module install will fail if:

• shell_exec is not available
• we are on a a non-Unix OS
• if Git is not installed.

function gitinfo_requirements($phase) {
  $route_name = \Drupal::routeMatch()->getRouteName();
  if ($phase === 'install' || ($phase === 'runtime' && $route_name === 'system.status')) { .. }

The rest can then be moved to a separate dedicated page but leaving the built-in check to avoid breaking.

It might be good to keep a link to the Git Info report. Rename to just "Git info".

Another advantage of this approach is that we now can give permissions to any role to view Git info, which is pretty harmless. Furthermore, we have now more horizontal screen space available as we do not use the left column for report sections anymore.

To see how to replicate the functionality of the Status report to have warnings places separately at the top.

The attached patch only leaves the Git version info on the Status report with a link to the detailed report that now lives at admin/reports/gitinfo. We now can give permissions to any role to view Git info.

• To see how to replicate the functionality of the Status report to have warnings placed separately at the top.
• Now that we have put the code in a class: \Drupal calls should be avoided in classes, use dependency injection instead
• Change the following text on the settings page:
  Configuration for the Git Info section in the Status reportReport.
  Connect with remote repos and check if your Git version is up to date

Using Drupal status messages for errors, warnings, and OK.