Investigate if rewriting to `cumulatives` is good for zero-length tasks when posting MiniZinc constraints `gecode_cumulatives`

In the [registry function](https://github.com/Gecode/gecode/blob/87a464b9d7d67616c1b4c6b98600d38a782d014b/gecode/flatzinc/registry.cpp#L1210) for `gecode_cumulatives` the case where the tasks may have zero-length duration and the bound is not assigned is currently decomposed into basic constraints.

An alternative re-write strategy would be to rewrite to cumulatives using multiple machines, where zero-length tasks are on a different machine with an "unlimited" bound.

If #81 has been implemented, this should be tested in the new MiniZinc rewriting, otherwise in the current C++ code.