Fix analysis mode of scheduling engine

[adrienmaillard]

• Tickets addressed: Resolves #1583
• Review: By commit
• Merge strategy: Merge (no squash)

Description

The issue arose in this case

• conflictSolverReturn was not initialized
• the analysis mode was ON
• the type of the conflict was something else than an association conflict so the variable kept being null

Initializing the conflictSolverReturn variable to its default state (unsatisfied, no activities created) fixes that issue and no other logic is impacted.

Verification

None.

Documentation

None.

Future work

None.

[Mythicaeda]

Would you mind quickly explaining why it was null to begin with, if you recall?

[adrienmaillard]

An oversight. Probably from before it had a default state via its default constructor.