Fix #1501: Generate WhenStateIs/WillSetStateTo correctly in ToCSharpCode

[Bafyn]

Summary

MappingConverter.ToCSharpCode generated broken code for stateful (Scenario) mappings: it emitted .WhenStateIs(NextState, TimesInSameState), which has no matching overload (does not compile), used NextState under WhenStateIs, and never emitted the actual ExecutionConditionState.

References

Fixes #1501

Submitter checklist

• The PR request is well described and justified, including the body and the references
• The PR title represents the desired changelog entry
• The repository's code style is followed (see the contributing guide)
• Test coverage that demonstrates that the change works as expected

Tests

• Added two MappingConverterTests.ToCSharpCode cases;
• Corrected two MappingBuilderTests.ToCSharpCode verified snapshots.

[StefH]

I just started also on this....

[StefH]

@Bafyn
Can you also update the Wildcardmatcher code to:

public override string GetCSharpCodeArguments()
{
    return
        $"new {Name}" +
        $"(" +
        $"{MatchBehaviour.GetFullyQualifiedEnumValue()}, " +
        $"new AnyOf<string, StringPattern>[] {{ {MappingConverterUtils.ToCSharpCodeArguments(_patterns)} }}, " +
        $"{CSharpFormatter.ToCSharpBooleanLiteral(IgnoreCase)}, " +
        $"{MatchOperator.GetFullyQualifiedEnumValue()}" +
        $")";
}

[Bafyn]

@StefH I realized you did when I noticed you assigned the issue to yourself 🙃
I can also look into this thing you mentioned #1501 (comment)

UPD: yes, checking

[Bafyn]

FYI @StefH the other matchers had the same issues. Fixed them in scope of the latest update

[StefH]

Added comment.

And if you have fixed an issue, you can "resolve conversation" here in the github.