Presently the Outbox Quarkus extension requires that an application use the same parameter configuration for all implemented ExportedEvent types. We should look at ways to allow a single application to work with varied generic signatures.

The big question is how would this be modeled at the database? With different types, this would mean the database table would be different for all variations and therefore would this mean we'd have different outbox database tables? If so, how do we coordinate their order or is that even a concern?