Migrate FREME NER to new architecture

[jnehring]

I added an implementation to the branch architecture-update. It creates a FREME package. Further it contains a unit test for "spot". Instead of loading an own spring application context, it loads the general FREME context and integrates in this context.

Next steps

• Move enrichment api endpoint to repository
• Move dataset management endpoint to this repository
• Create proxy endpoints for broker. This will be a generic proxy implementation that forwards API requests.

[jnehring]

Done

• moved enrichment api endpoint to repository
• move dataset management endpoint to this repository
• implemented create / read / update / delete endpoints

Current problems

• PUT creates an empty dataset without content and with a dublicate name instead of updating the existing dataset.
• Sometimes the create dataset method crashes. It creates the database entry but does not write any triples. Sometimes it works.

Larger problems (will not be fixed within this issue)

• Apparently there is no transaction management implemented. When something fails (e.g. writing to SolrServer) then have inconsistent database entries.
• FremeNer uses database entities without users.

[jnehring]

Above "Current problems" have been solved.

Next steps:

• Update the master branch
• Install FREME NER on freme-worker, also with Jenkins (#43)
• Install the proxy in the broker that redirects calls to FREME NER (https://github.com/freme-project/basic-services/issues/27)

[jnehring]

Done:

• Install FREME NER on freme-worker, also with Jenkins (#43)
• Install the proxy in the broker that redirects calls to FREME NER (freme-project/basic-services#27)

Last step:

• Merge in master branch

[jnehring]

I merged the changes in the master branch. Further I stopped the old dev installation of freme-ner. So this task is finished.