Clean up ConflictBuilder and ConflictBuilderParallel

[WJSchakel]

The classes ConflictBuilder and ConflictBuilderParallel are huge classes with considerable overlap, between them and within each. The parallel code that was added is not well documented. It should be investigated whether the code is ready. There are big tasks (from one lane, consider all later in list of lanes), and small tasks (consider specific lane combo), what to do with these? The builders are also quite verbose.

[WJSchakel]

ConflictBuilderParallel was removed. Documentation in ConflictBuilder was improved, particularly on the parallel implementations. There are two parallel implementations:

• Small; between two lanes.
• Big; between one particular lane, and all lanes further in a list (i.e. similar to a triangular matrix procedure).

This issue will be closed now. In the future it may be re-opened to:

• Use record classes for the data holders of each parallel task.
• Use fibers for parallel task execution, and remove the big task type.