[FEAT] CasePathResolver: let provide options to tune the path computation

[tbouffard]

DISCLAIMER: this issue describes path computation for a single instance/case only. So the implementation will go to the CasePathResolver class as it differs from PathResolver which is a generic implementation that both deals with single instance or all instances of a process.

We already have several use cases that requires options to be enable.
The name of the options should be consistent in particular the usage of singular or plural.

Here is a list of issues involving options:

• [FEAT] CasePathResolver: handle "forward lonely edge" from an exclusive gateway targeting a merge exclusive gateway #10 and [FEAT] CasePathResolver: handle "forward lonely edge" from an exclusive gateway targeting a BPMN Activity #175
• [FEAT] CasePathResolver: detect start/end event #12
• [FEAT] CasePathResolver: detect start/end event in "lonely edge" branch #13
• [FEAT] CasePathResolver: handle "backward lonely edge" with exclusive gateways #14
• [FEAT] CasePathResolver: infer "holes" in the path #19
• [FEAT] CasePathResolver: detect BPMN links #20
• [FEAT] CasePathResolver: categorize the elements returned in the inferred path #24 to choose if candidate should be returned
• [FEAT] CasePathResolver: Allow to infer pending elements #145
• [FEAT] CasePathResolver: Infer incoming/outgoing flownodes/edges of Parrallel Gateways #146