Fix member role capabilities

[gmaclennan]

Description

Currently the capabilities for a "member" role is the same for all schema types:

{
  readOwn: true,
  writeOwn: true,
  readOthers: true,
  writeOthers: false
}

I think this is incorrect. The terminology is slightly confusing here: writeOwn means you have permission to create a record of the given type. writeOthers means you have the permission to edit a record created by someone else.

I think a project member should only be able to create these record types: coreOwnership, deviceInfo, observation. They should not be able to create: field, preset, icon, translation, role.

Tasks

• Update the member role docs permissions