When using the Quarkus outbox extension, one cannot have additional custom columns (which would then be picked up and e.g. propagated as header properties by the event routing SMT). Can we envision a model, where a user can add further fields/columns to their outbox event types?