Properties without explicit permissions declarations are no longer displayed and made editable by default

[brianjlowe]

Describe the bug
Prior to 1.15.0, properties could be added and displayed without having to set the role levels. This meant that someone could load an ontology and start to use it in VIVO without additional work. Now, it appears that every loaded property one wants to display publicly or make editable will require perhaps as many as 21 individual checkbox clicks in the ontology editor form. This makes it impossible for an end user to import an external ontology in the GUI and use it without scripting or CONSTRUCTing the necessary permissions settings.

To Reproduce
Steps to reproduce the behavior:
minTest.n3.txt

1. Go to Site Admin -> Add/Remove RDF -> Add mixed RDF / N3 format: upload attached minTest.n3.txt file.
2. Search for "Jane Doe" or "John Doe". Note that their profiles pages are empty for non-root users. (Use an incognito window to view if logged in as root.)

Expected behavior
Do the same as above in a version prior to 1.15.0 and each profile page will display the "friend of" to public users. Find the "friend of" object property in the ontology editor in < 1.15, edit it, and the permissions dropdowns will default to "public" for display and publish and "any user who can log in" for update.

If we no longer want to default to making properties visible and editable, we need to offer an easy option when loading ontology RDF (perhaps also via filegraph) to assign the permission properties in bulk. (It would also be nice, if one does want to set the permissions on an individual property, to have some "select all / deselect all" functionality so that one doesn't have to click so many times. In the past there were just three dropdowns which weren't so bad.)