Members query that takes an ID instead of a resource

[escowles]

We recently encountered an issue where we are passing a resource's ID to a job, and then need to do an extra query to load the resource in order to find its members. It seems like many implementations could do the query with just the ID, so maybe we should add a members query that takes an ID instead?