Release v4.6.2

Fixed

• A command in the sandbox runtime no longer reports success when Chronicle rejects its events. A constraint violation now fails the command with the constraint's name and message as a validation failure. A schema rejection or any other append error fails it with an error. Before, the rejection was only logged, so nothing was appended and read models stayed empty while the command said it had succeeded. (#10)
• $context.tenant and $context.causedBy.subject, .name and .userName in produced event mappings now resolve to the current tenant and caller. A produced mapping the runtime cannot resolve now fails the command instead of being dropped from the event. (#10)