Fix changes-detected dialog text (i18n pointing to wrong entry)
Backend changes to switch subjects to use the new Relationship mixin instead of URI strings
Replace container_location with a relationship definition and remove the dedicated type.
Remove obsolete container_location model
Refuse to resolve raw URI strings: references must now be of the form {'ref' => '/the/uri/to/be/resolved'}

Modified a couple of test cases that were doing the wrong thing--the
rest look fine.
Reintroduce the 'container_location' schema in its modified form.
WIP get container locations working in the frontend
Fix container_location read only view (show template)
Revert overflow:hidden on accordion body (was visible to allow popover to be seen) - and now allow tokens to have their popover position configured
When deleting a record, delete any defined relationships too
Added tests to cover the new relationship deleting behaviour (and to catch the original bug)
Change the way refs get resolved.  Previously we would resolve a ref like:

  'property' => {'ref' => '/some/uri'}

to:

  {
    'property' => {'ref' => '/some/uri'}
    'resolved' => {'property' => {resolved version}}
  }

but now we inline it into the ref itself like this:

  {
    'property' => {'ref' => '/some/uri', '_resolved' => {resolved version}}
  }

This has the nice effect of keeping everything together, so you can access the
resolved version at the same path as the ref itself.
WIP update linker and references to 'resolved' to hit the new '_resolved'
Chop out mystery bit of handle_crud
Mark broke everything WIP
Deserialise JSON blobs coming from the linker widget before they hit the templates
Remove "ref" from the resolve[] list from controllers.  Replace with the property actually being resolved.
Fix integration tests for new resolve approach
WIP add related_accessions template/linker refactoring
Remove munge_related; only render the lock_version hidden input if exists on the object; clean up accession linker to work as a one-token input