Currently, the content/move has a direct dependency on the content/remove policy.

This makes it impossible to, for example, allow users to manage content within the tree, without having the ability to remove nodes with certain object states.

Steps to reproduce:

1. Create user of Role with content/move policy (but not content/remove)
2. Login as that new user and attempt to move content, you will receive an error message
3. Add the content/remove policy to the user's role, and try again, the error will no longer be present