When dragging and dropping nodes in trees, don't touch the lock version of affected records.

This prevents problems when the user has an edit form open, manipulates the
tree, then submits the form.
Make db:nuke delete Solr data dir using full path

Also change task description (was same as db:migrate)
Merge pull request #434 from anarchivist/nuke-it-from-orbit

Make db:nuke delete Solr data dir using full path
WIP make position sticky after move (when form is open)
Update the tree.js to update the position of the selected node when nodes are moved (to ensure it's hidden input value for position is kept up to date)
Rejig orderable
Merge pull request #433 from hudmol/tree-change-locking

When dragging and dropping nodes in trees, don't touch the lock version ...
WIP first got at a basic RDE form
WIP try a horizontal form
WIP add backend handlers for adding bulk children
Make a backend handler for Resources to add multiple children
Make a backend handler for Archival Objects to add multiple children
WIP Redo the RDE templates and get some kind of submission working in the frontend;
Tweak some things and rm the old template