Allow access to admin/reports based on the 'access administration pages' permission

Not having 'access site reports' control access to 'admin/reports' sounds very counter intuitive to me and would probably lead to confusing as to what that permission actually does. Because, what does it actually do if this would land? Only control access to the recent log messages? If the problem is with exposing the recent log messages with this permission, doesn't it make more sense to give that its own permission?

Having fine grained control over who sees log messages makes more sense to me.

A new permission to view `Recent log messages` makes sense. However, the top-level item for admin/content and admin/structure already use the `access administration pages` permission so maybe both?

Setting to NW for the change record. And possible more discussion in #25 + #26

Alternatively, what if there was a separate permission for "access reports overview"? It's a similar use case to wanting to give users access to the node overview page without granting them the ability to edit all nodes.

Our use case is that we are adding some additional reports that we want some of our content editors to use but we don't want to give them the permission to view all the developer-facing reports that Drupal ships with.

Reroll after 🐛 Restrict access to empty top level administration pages Fixed was committed.