Create testcases for all the different ordering scenario's when closing a zaak

[MLenterman]

There is a lot of complexity surrounding the closing of a zaak. Most scenario's are already covered in the bigger end-to-end scenario's, but there are no asserts to validate the zaak closing behavior on those. We would like dedicated testcases for specifically testing the zaak closing behavior.

• updateZaak sets einddatum before eindstatus is set. ZaakBrug closes the zaak by adding eindstatus with datumstatusgezet of einddatum. If in a later message eindstatus is set afterall, it should not be added a second time and no error should be thrown when the duplicate is detected.
• updateZaak or actualiseerZaakStatus sets eindstatus without setting einddatum on the zaak. ZaakBrug simply adds given eindstatus.
• updateZaak sets eindstatus and sets einddatum. ZaakBrug simply adds given eindstatus.
• Same 3 default zaak closing scenario's, but now a resultaat is not present on the zaak yet when closing and there is no entry configured for the zaaktype in the translation profile in profiles.json. It should result in an error.
• Same 3 default zaak closing scenario's, but now a resultaat is not present on the zaak yet when closing, but now there is a "endDateAndResultLastStatus" entry configured for the zaaktype in the translation profile in profiles.json. ZaakBrug should add a (dummy) resultaat of the configured resultaattype from the translation profile before it sets the eindstatus and closing the zaak should succeed. In a following updateZaak when resultaat is set afterall, the given resultaat should replace the injected (dummy) resultaat and not throw any errors.