Release v22.40.1

Fixed

• Screenplay generation names the declared enumeration member, including a [Flags] zero member and a member declared as a combination of others, when a scenario's expected event states it in a ShouldHaveAppendedEvent predicate, and does so for enumerations declared over byte, long and other integral types as well. The generated document no longer fails with "not a declared member of enum". (#2839)
• A scenario that issues a command, starts from an event or expects an event with a value the generated document cannot state is now left out and reported as a warning (SP0039) naming the property, the value and why, instead of being written as a number, under an invented name or without the value, and the document no longer fails to compile on such rejection scenarios. The values are a number cast to an enumeration that declares no member with it, default for an enumeration that declares no zero member, several [Flags] members combined into a value no member is declared with (Screenplay cannot state combined flags), and null for a required record or list. null is still stated where the property may be absent. (#2920)