Fixed wrong function order after upgrading remapped functions
Fixed wrong function order after upgrading remapped functions

function upgrades did not update the position for remapped
functions, causing them to get called in the wrong order.

This breaks many VTK workflows, with failed and broken renderings.

vistrails/core/upgradeworkflow.py:
- UpgradeWorkflowHandler.replace_generic:
  Add correct position to new functions

Test case:
Copy and paste first node in examples/vtk_examples/GUI/VolumeRenderWithBoxWidget.vt
Trigger upgrade, copy vtkVolume16Reader to text editor to compare functions before and after the upgrade.
Check that "DataByteOrder" is called before "FilePrefix", otherwise the rendering
will be corrupt. (Pipeline has other problems and needs python-wrapper branch to run)

TODO: Proper test

minesense/VisTrails,VisTrails/VisTrails,minesense/VisTrails,minesense/VisTrails,VisTrails/VisTrails,VisTrails/VisTrails,VisTrails/VisTrails,minesense/VisTrails,VisTrails/VisTrails,minesense/VisTrails