Move location of inspector page to reports.

Yeah it was originally in reports, see https://cgit.drupalcode.org/config_inspector/commit/?id=65e319a816db83ff... where we moved it out of there. More feedback on the desired location of this would be nice, so we don't keep moving it around. Unfortunately that was moved without an issue. If there would have been an issue at the time, we could see the discussion that happened then :)

Drupal Core has a similar inspection for entity definitions that is reported on the 'Status report':

I would suggest to make a similar entry for configuration entity schema errors and revert 65e319a816, in line with the Entity definitions mismatches reported by Drupal core.

+1 for moving into reports and including configuration errors on the status report page

Filed #3009151: Show configuration schema errors on the status report page to prevent scope creep for this issue.

It is not just about reverting 65e319a816 as there are all the routes defined in the routing.yml that would still be using the admin/config path. I am fine with moving it (back) there, can someone please provide a patch? Also a screenshot of the reports page would be nice so we can see if it fits in with the other items. Thanks!

Attached patch implements the following changes:

1. Adds a menu link to admin/reports/config-inspector from #2757413: Create a menu item for the inspect page
2. Removes the local task for the overview page, since it is not really on the same level as the other tasks.

Screen capture after applying patch:

Thanks. The reason I was looking to have a screenshot of the reports page is that if you look at the menu items, neither has a verb in it, after all its reports, not things "to do" but things to "look at" :) I wonder what would be a better menu item title for this that fits better with the reports menu items. "Configuration" would come naturally but that may be misleading for some believing they would configure their reports. Maybe "Configuration inspector" would be best? That leads with the word you are looking for but not misleading. Also matches the module name :D

#9 I agree that 'Configuration inspector' is a better label. I updated the patch accordingly.

Thanks!