Support lazy actor evaluation

If we make it part of the check behavior to express which parts of the actor it needs to access, and when we support arbitrary calculated fields in ash core, we could support lazy actor evaluation if the actor is a resource. This could allow them to start a request pipeline with just a user id, and the authorizer will request data as it becomes necessary.

The issue names no files, tests, or entry points. Start by tracing check behavior and the support for arbitrary calculated fields in Ash core, then determine how an authorizer could request actor data only as needed. Done means a request pipeline can begin with only a resource actor's user ID and load further actor data lazily when authorization requires it.

Written by the indexing model from the issue text.