Add ability to query resource access activity

The ability to control who/what can access specific resources in your pod is great. An important complement is to be able to see how and when they are using this access.

Being able to query how the access you've given is being used is a great way to determine whether those grants are too broad, still necessary, or being abused.

Extreme caution needs to be taken in how this is designed, lest it turn into an avenue for denial of service. For example, limiting it only to those requests that successfully pass authorization would restrict any recorded activity to entities that should have some semblance of trust already. Similarly, recording and updating only aggregate metrics may reduce resource usage without losing much practical value.

Start by reviewing the Solid specification areas covering resource access control and authorization. Define how access activity should be queried, what successful requests are recorded, and whether aggregate metrics are sufficient, while assessing denial-of-service risks. Done means the specification resolves these design questions and documents the resulting behavior.