Enforce 1.0 encoding for scripts/shares (See #11322)

In order to be able to migrate to Ice 3.5 and then back to Ice 3.4 (or even be able to re-use a database between the two), it's necessary to force Ice to use the old (1.0) encoding in some situations. Namely, all shares and all script parameters should be stored in the old format. This can be tested by building with Ice 3.5 and then configuring a new OMERO instance, creating shares and launching scripts; followed by building with Ice 3.4 and talking to the same DB (regardless of client version).

I could not specifically reproduce the errors seen in http://trac.openmicroscopy.org.uk/ome/ticket/11322, but this should be the most conservative approach we can take for 4.4.9.

Note: `Ice.EncodingVersion` is not being used because it was
first introduced in 3.5 meaning that this code would not be
compilable with the other zeroc jars.