Fix coverage conversion rule for otherwise

[killy971]

A custom conversion rule for the otherwise statement was added by #3.

This change introduced a problem: lines containing the otherwise statement will always be converted at least as partially covered, even if they are never run at all.

In order to fix this problem, the custom coverage conversion rule should be made aware of other coverage data for the same expression.

[killy971]

An otherwise expression is represented by the 3 following BoxLabel values:

• ExpBox False,
• BinBox GuardBinBox True,
• BinBox GuardBinBox False.

A simple way to apprach the problem would be to change CoverageEntry type to the following definition:

type CoverageEntry = (
    [MixEntry], -- mix entries
    [Integer],  -- tix values
    [String])   -- entry source code

The MixEntry list would contain all mix entries which share the same HpcPos

[killy971]

From the current implementation, one way to proceed would be to create a function signature:

[(MixEntry, Integer, [String])] -> [([MixEntry], [Integer], [String])]

to aggregate the current mixEntryTixs values based on the HpcPos value.

[killy971]

Fixed by 17c6f99