#26908 Added flame clip updater to nuke multi publish

This adds a new secondary task for the nuke publish which updates the clip xml for the current shot:

![screen shot 2014-12-12 at 16 27 41](https://cloud.githubusercontent.com/assets/337710/5416931/75acf72e-822c-11e4-9e83-252067670d8b.png)

When the flame box is ticked, items will appear in the version dropdown for that clip in flame:
![screen shot 2014-12-12 at 16 33 35](https://cloud.githubusercontent.com/assets/337710/5416941/9504469a-822c-11e4-853e-d71bcd4e4e52.png)



Any worry about negative values ? 
What about frame ranges requiring a bigger padding than 4 digits ? I know a studio doing commercials which uses camera timecodes converted to frames for image sequences, to ease editorial changes handling ( no arbitrary renumbering from 1001 ). In that case, frame numbers can be huge. Is there any limitation on the Flame side which would make trying to be smarter pointless, e.g. matching the padding from the SEQ field ?