Submission Permission fixes

[naglepuff]

Fix #1162
Fix #939 (temporary/non-ideal fix)

This PR addresses additional issues with assigning permissions from the UI and adds some UX enhancements like banners and tooltips.

List of Changes

Don't Override PI Owner Role

If the same ORCID iD was used for the PI ORCID and as a contributor ORCID iD, then the permission level set at the contributor level had priority over the ideal PI level (owner). Now, priority is given to the owner role when building the request body to update the submission with new permissions.

Validate address without rendering form

This is a "fix" for #939. The address form now validates by investigating data in addition to through Vuetify's form validation. Vuetify's form validation was insufficient because the address form cannot be validated by it until it is opened. The previous workaround for this was to open the form, which would be validated upon render by Vuetify, and then close the form. Metadata Contributors are unable to do this, and would be stuck at that screen. The only workaround for those users would be to replace /context with /samples in the URL.

The reason this fix is not ideal is because it duplicates validation, so changes to validation rules for this form need to be applied in two different places.

The address form dialog now uses the eager prop, which forces it to render and thus validate when it mounts. (thanks @marySalvi)

Add Permission Level Descriptions

A tooltip has been added to the Study form describing each permission level.

Add Banner for read-only views

If a user is presented with a read-only view due to insufficient permissions to edit the current form, a banner now appears informing the user of this.

Prevent PI from changing their own ORCID

If the current user is the PI, don't allow them to edit the PI ORCID field on the study form and remove their permission.

[marySalvi]

One minor change but otherwise looks good!