Isolate edge and origin DAF logic, demonstrate own resource relationships filtered by privilege

Origin properties do not need privileges. Relationships access directly through an edge request, through request fields, and through body attributes (such as during a patch) do need privileges.

The approach should be to implement the current access rules through a DelegatedAdmin RequestVisitor along with adding support for relationship fields filtered by privileges.

1. Access rules removed - Should work for origin, relationships and edge.
2. Access rules left in place - Should work for relationships and edge with original rules handling origin requests.
3. Document how to move/update to DAF handling origin ownData from using access rules. -> remove access rules, enableDynamicRoles : true, ...
4. Determine precedence of schemaConfig such as isViewable/userEditable over privileges that have permission otherwise.

EDIT: This will not be enforced by Java. Customer needs to understand their own implementation with access.json rules, router-authz customizations and custom-authz customizations, and then create privileges that work with them.
The reason behind this is the fact that we cannot enforce something natively in the source that is meant to be configured/customized by the customer.

In terms of being able to make privileges for accessing your own data, a filter of "_id eq '_id'" on the privilege will apply that privilege only to a resource where its _id matches that of the authenticated resource.