Clarify the related agents code by naming the date handling method.
Generalise related agents code to let us model relationships that have directions.
Change the way we store relationship directions so it works for non-global records too.

Previous we would store 'relationship_target', which was the URI of the
record that a relationship pointed to.  This worked fine for global
records, but could be troublesome for repository-level records, as these
can have different URIs over their lifetime if transferred between
repositories.

Now we store a pair instead: the record type and its ID.  This should be
stable throughout a record's lifetime.
Change the new directional relationship API to be a drop-in replacement for define_relationship
Add backend implementation of hasPart/isPartOf
Add support for the bound_with relationship too
Switch both relationship types to use the same JSON property
Frontend changes to support the new types of accession interrelationships.
Make sure related accessions don't interfere with spawning resources.
Code review suggestion: use the display string when showing related accessions in the read-only view.
Merge pull request #769 from hudmol/accession-to-accession-relationships

Accession to accession relationships
added material types subrecord to accessions
tidy up the display in read only view
added placeholder for material types help topic
fixed alpha order of columns as this seems to drive the order in the readonly view
added some tests
use an anchor to avoid duplication
scope should be global
i18n truth values in the form helper
shuffle migration to the end of the line after rebase