New API: Add api end point to move datasets

[kcondon]

We frequently get support requests to move datasets. Adding an API endpoint to do this would be empower end users to do this.

[mheppler]

Related/duplicate of #2226 from 2015-06-01.

[djbrooke]

Questions from backlog grooming:

• How are guestbooks handled? Versions? Templates? Groups?
• Doing this first makes New API: Add api end point to move dataverses #4406 easier
• If not superadmin only, what permissions are needed on both dataverses?

[kcondon]

Note: we currently move a dataset by updating the owner_id in the dvobject table to be the new parent dv and the indexing the moved dataset:

Move dataset, id=16 to dataverse, id=6:
update dvobject set owner_id=6 where id=16;
Index dataset:
curl http://localhost:8080/api/admin/datasets/16

Note: when moving dataverses (another ticket) you do not need to move their child datasets directly but you do need to reindex them.

[sekmiller]

Slight change in process for datasets with guestbooks being moved to a dataverse where that guestbook is not available. The user is warned that the guestbook is not in the target dataverse and that she may use 'forceMove=true' to complete the move. The guestbook is then removed from the dataset.