support user specification of timeFormat and precision for ensight output cases

Currently the ensight cases use a hard-coded time format (usually scientific) and precision. When the time-steps are very close to each other, this lose of precision makes the time names indistinguishable at later processing.

Add user-configurable specification of time format and precision for ensight volume/surface/sets writers. cross-ref EP2297