Change internal data format to `expanded` JSON-LD

Triggered by the update to Elasticsearch 0.90.5 (see #110), which
complains about an inconsistency in our previous data format:

With `comapct` JSON-LD, plain literals are serialized as strings,
while e.g. literals with a language are serialized as an array of
objects with `@value` and `@lang` keys. This results in different
types for the same field (here: string and array).

Since Elasticsearch requires that a specific field has a consistent
type, this commit changes the JSON-LD serialization to use the
`expanded` format, which always encodes literals as object arrays.

At the same time, the API still serves the `compact` format, so
clients should not have to change their result processing logic.

As the format of the data created by the conversion from N-Triples
to JSON-LD has changed, this commit increments the version number
of lodmill-ld to 0.2.0-SNAPSHOT.

It also deletes the Eclipse project config files in lodmill-ui,
which have to be generated locally with `play eclipse`.
Merge pull request #166 from fsteeg/issue-111-hadoop-1.2.1

Update to Hadoop 1.2.1
Rename method for better clarity
Fix wrong rdf/xml root element
Add gnd-rdfxml-splitter-serialization test
Remove redundant test
Update README for new Elasticsearch version 0.90.5 (see #110)
Merge pull request #169 from dr0i/gnd-updates

Gnd update: splitting rdfx/xml so that every entity is serialized as a single rdf file
Reconcile job and indexing scripts (see #171)
Fix xml escaping
Add back dewey-by-label tests and sample query

Previous issue (see #119) no longer occurs with current data
Merge pull request #178 from dr0i/gnd-updates

Fix xml escaping
Merge pull request #176 from fsteeg/issue-171-scripts

Reconcile job and indexing scripts
Add `http://purl.org/dc/terms/subject` to resource view
Merge pull request #172 from fsteeg/issue-110-es-0.90.5

Change internal data format to `expanded` JSON-LD and update to ES 0.90.5
Merge pull request #177 from fsteeg/issue-119-dewey

Add back dewey-by-label tests and sample query
Handle blank nodes with identical labels from different files

Since blank nodes from different files may have identical labels,
we add the file path to the node identifier used to track blank
nodes for which we want to resolve details (see #109).
Add `http://purl.org/dc/terms/language` to resource view (see #180)
Actually link to `api.lobid.org` from main header (for proxy)
Merge pull request #185 from fsteeg/api-link

Actually link to `api.lobid.org` from main header (for proxy)