Release v22.58.3

Changed

• Command scenarios whose only failure assertion is ShouldNotBeAuthorized, ShouldHaveExceptions, or ShouldNotBeSuccessful are no longer generated as rejections, because they do not prove a validation or constraint rejection. They are omitted and reported as unreadable specifications. (#3046)

Fixed

• The generated Screenplay model keeps identifier and the for destination on a command whose handler returns an event together with a separate response, (TEvent, TResponse), including through Task and ValueTask. Such commands no longer report SP0013/SP0051, and their specifications no longer run as unsupported identity allocation. A response typed as an event source identifier, object, an interface, or a union that can carry an identity still leaves the destination unstated. (#3069)
• A command scenario that only asserts the command was rejected, such as IsValid.ShouldBeFalse() or ShouldHaveValidationErrors(), is now generated as a bare then error that binds and matches the rejection without asserting a message, instead of then error "". (#3046)