Script paths to basename 11464

[will-moore]

This fixes https://trac.openmicroscopy.org.uk/ome/ticket/11464 where several scripts use a filename coming from a script parameter without checking whether the filename is actually a path.

For each of the scripts in this PR, we validate that the file name is only a name using os.path.basename().

To test:

• Run E.g. Movie Figure script in Insight, using an image that is named like: path/to/the/image.dv
  The path will be removed and the figure should become named "image.jpg".
• You can try this with a few of the different scripts (include Batch_Image_Export), but probably not worth doing all of them. I've already tested them all and they all have exactly the same commit applied.

[joshmoore]

Is there a reason that we use the actual requested filename in the script, rather than just uploading to that name. The one place where it's required looks to be the folder_name of the zip in batch exporting.

In terms of a more central solution, the only thing I have thought of so far is a "Filename" parameter type which is automatically sent through os.path.basename.

[bpindelski]

Tested with howe and insight - all looks good. Path elements are stripped out.

[joshmoore]

Only side question, @will-moore, is if you also looked at omero-user-scripts@examples for any of these issues. Merging.

[will-moore]

Doh - I have just done as @joshmoore suggested and only used the supplied file name for naming the uploaded original file (not for writing locally).

I'll open another PR

[joshmoore]

Sorry @will-moore!

[sbesson]

--rebased-to #42