Lifecycle Job Rules: handle unchanged files without iteration.

[koechlm]

Unchanged files should not increase iterations; today, user rule execution allows the management of changed/unchanged files, whereas lifecycle-driven rule execution creates new file iterations in all cases.

• consider implementing an admin option like user rule administration offers; this would allow enforcing an undo check-out even if the file dirtied during the rule execution
• consider dynamically handling the file according to the dirty state at the end of the rule execution.
• consider combining both, for the highest flexibility: handle dynamically, but respect a preference of saving/not-saving in case of modifications (dirty flag).
  The combination might be of value for user rules as well.