Users with write permission cannot update system metadata

[laurenwalker]

Step to reproduce:

• Create a resource map, EML, and data object but only give yourself read and write permission on these objects, and make someone else the rightsHolder
• Send a request to updateSystemMetadata() for one of these objects, with only the fileName value changed.
• Notice a 401 error is returned that says you do not have CHANGE_PERMISSION permission.

Proposed changes
I think we should allow updates to the rest of the system metadata, particularly the fileName and formatId, to anyone that has write permission. I am guessing we have chosen to deny all system metadata updates to users without changePermission for simplicity, but now that we are adding access policy editors and file name editors to MetacatUI, this issue is going to pop up a lot.

MetacatUI will have to start restricting renaming to only those with changePermission, which seems overkill. OR, it will have to perform an entire object update() just to rename the file (which is actually a loophole in which the user could change the access policy anyway... see #1450)

[taojing2002]

The change of the system metadata may involve the modification of access rules, which need the changePermssion. So we have to do this way:

1. If there are no changes on access rules, write permission is required.
2. If there are some changes on access rules, change permission is required.

We need to develop code to compare access rules.