Consider the following request:
If not all the resource collections for "authzRoles" are defined in the schema, then the augmentation filter will fire "READ" requests to fill in missing data that the VertexEdgeTableHandler wasn't able to retrieve in the mega-query.
- create a user that has 2 authzRoles, ont that is internal/authzRole and one managed/role.
- modify the managed.json file and remove manage/role as a resourceCollection in the authzRoles relationship.
- create a priv against managed/role that would filter that added role to the user.
and ensure that only the internal/role is there.
Acceptance criteria: need a jdbc unit that covers this setup.