AKScheduling: Fix constraint violation generation for conflicting slots

Currently, the AK belonging to the second conflicting slot is not properly added to list of AKs belonging to this constraint violation, causing the violation not to be correctly updated/removed when the second slot is moved or deleted afterwards. There might also be additional problems when slots are deleted after scheduling (further investigation needed).

changed the description

added bug label

changed milestone to %KIF 50,0

assigned to @bhaettasch

Seems like this was always caused by deleting slots. I will add an explicit handling of slot deletion.

mentioned in commit a3ccf65b

mentioned in merge request !118 (merged)

mentioned in commit 8b5ffde8

mentioned in commit ba15b01d

closed with commit 8b5ffde8

closed with merge request !118 (merged)