Explicitly specify schemas for sequences

You would need to have a lot of alliases in oracle db otherwise
Merged export controller and services from rc2_dev branch

Also split the exportService into a metadata part and an export part.
However, no extra changes or improvements were made to make the export
work. Just the code is merged.
Merged frontend code for exporting from rc2_dev
Merging changes in dataExportService from rc2_dev to use core-api for
exporting
Merge pull request #51 from thehyve/improvements/explicit-schema-specification

Explicitly specify schemas for sequences
Merged even more export code from the rc2_dev branch to make exporting
work.
Removed references to the core-db, as well as unused imports
Remove 'created by ...' comment

We decided not to include those
Removed reference to core-db in export functionality.

This commit depends on changes in core-db (commit 930b474) and core-api
(commit 8906be9).
to increase dalliance plugin version
Merge pull request #54 from thehyve/features/update_dalliance_plugin

Features/update dalliance plugin
Reimplemented counting patients with clinical data
Adjusted export to also handle non BiomakerDataRow objects
Update gmock
Add runtime dependency on javassist
Add CurrentUserBean
Add QueriesResourceAuthorizationDecorator

Wrapping QueriesResourceService, with access checks.
Adapt to addition of QueryResult::getUserName
QueryToolController: check access and save username
Merge remote-tracking branch 'origin/master' into features/FT-835-merge-hd-export