Make Locations Global:

Remove repo_id column and foreign key from the location table

Set the location scope to be global

Update the uri in the location schema

Remove repo_id from the backend controller params and convert the update_location_record permission to be global

Remove repo_id from GET /locations endpoint

Derive the update_locations permission from the update_arhival_record for now

update tests

update reference to locations/batch endpoint in the frontend

Derive the update_location_record permission from the manage_repository.

Only Admin and Repository managers can update location records.

Modify User#can? to not raise an error when the derived permission is not given to the user, instead return false.

Patch the tests to take into account the new derived permission off manage_repository.

Fix selenium test as archivists cannot edit locations

Add a selenium test to cover permissions and global access of locations

Added a test for locations being global on the backend

Added a selenium test for updating a location

Assume all derived permissions are global and set their level to global to express this

Store the derived permissions against the repository-level permissions too