change relevant fields to text or big varchar

Change relevant fields (i.e. name) to text or a big
character varying limit (i.e. 4096 for paths), for
the following tables:

  - entities
  - categories
  - formalitylevels
  - licensemodels
  - links
  - logics
  - languages
  - metadata
  - ontologies
  - ontology_types
  - ontology versions
  - oops responses
  - projects
  - repositories
  - resources
  - sentences
  - serializations
  - tasks
  - teams
  - tools
  - url maps
  - users

As requested these changes are applied into one massive
migration. This also includes the necessary adjustments
to model-column based tests.
add test for not displaying mapped symbols

If a symbol A is mapped to another symbol B, we should
not display (or actually register) symbol A for the
ontology to which the mapping is applied.
ensure non-exec of symbol callback in link

When in a symbol-mapping link (DGLink which contains
a map element) we should not execute the callback
for a symbol, as this will create the symbol
as part of the current ontology. And this not really
what we want.

Oh by the way: The spec is green.
fix keyword-compliance for worker

When using sidekiq to create and manage jobs, the arguments
to the async_perform call will be converted to JSON in order
to store them in the redis database. When the job is executed
the JSON is parsed into ruby types. However symbols get lost,
as JSON actually only supports strings.

Generally this is not a problem, as we usually use symbols
for their memory uniqueness
(which makes them faster and more pleasing to the eye).
But the ruby keyword syntax requires the hash to contain of
symbol keys. As the keys are now strings it will not recognize
this as a keyword-based hash. So we need to figure this out for
ourselves. This commit will take care of that with regards
to the 'try_count' key in our workers.
create common base-worker to dry up the worker

Especially with the new change (keyword-syntax compliance)
the workers were in need of some drying up.
This creates a common base-class and uses it.
make commits list more compact
remove save_current_ontologies
improve column widths in commit list
Merge pull request #837 from ontohub/610-remove_uncalled_function

remove save_current_ontologies
add spec for ext-references in DOs

If a single ontology in a distributed ontology references (i.e. imports)
an ontology which is not part of the distributed ontology, the
link/mapping should be created correctly and without failure.
support references in distributed ontologies

distributed ontologies (actually single ontologies in distributed
ontologies) can also import and reference ontologies which are not part
of the distributed ontology. So we cannot use `iri_for_child` to infer
the ontology-iri on ontohub for a referenced DGNode name. Instead we
create an ontology aliasing map which maps DGNode names to their
corresponding ontology-iri, which is determined when creating/finding
the specific ontologies.

This leverages the fact that DGLinks are always placed after the
DGNodes in hets-xml output.
use hets-xml fixture to not trigger remote network

In order to not use a remote network connection to
find the referenced ontology, we (sadly) need to
use a hets-xml output fixture.
Merge branch 'staging' into 765-references_in_distributed_ontologies
Merge pull request #823 from ontohub/767-avoid_symbol_creation_caused_by_mapping

767 avoid symbol creation caused by mapping
Merge pull request #811 from ontohub/534-adjust_possible_overlength_text_fields

534 adjust possible overlength text fields
improve decision for html or plain text sending of file
remove unused message css class
Merge pull request #832 from ontohub/300-compact_history_view

make commits list more compact
use proper http accept record
Improve OWL API request header check

Now, we use accept header ordering computed by
rails. As long as the q-values don't change, in
their ordering, we have more robust code now.

This code is about to be deleted/reverted together with
0a4106958a2950ecde156cacae0e9702dc819867.