[Feature] Unused fields in conditions should be zero

**Is your feature request related to a problem? Please describe.**
When first creating a quest state condition (e.g. for phase_area) with flags 2|8 and then changing the exact same condition to objective complete and generate SQL the generated data will contain the 2|8 in ConditionValue2 from the previous condition.

**Describe the solution you'd like**
Zero all unused fields of the used condition on sql generation

**Additional context**
Setting initial conditions
Changing condition type
Generating sql results in
```sql
DELETE FROM `conditions` WHERE (`SourceTypeOrReferenceId` = 26) AND (`SourceEntry` IN (493));
INSERT INTO `conditions` (`SourceTypeOrReferenceId`, `SourceGroup`, `SourceEntry`, `SourceId`, `ElseGroup`, `ConditionTypeOrReference`, `ConditionTarget`, `ConditionValue1`, `ConditionValue2`, `ConditionValue3`, `NegativeCondition`, `Comment`) VALUES
(26, 5950, 493, 0, 0, 48, 0, 12341234, 10, 0, 0, 'Player has completed objective 12341234 (but hasn\'t rewarded quest yet)');
```
(Notice the 10 for ConditionValue2)

Start by tracing SQL generation for quest state conditions from the condition editor, using the reported transition from phase_area to objective complete as the reproduction case. Ensure generated INSERT data sets fields unused by the selected condition to zero, and verify the output no longer preserves the previous ConditionValue2 value.

Written by the indexing model from the issue text.