Support Complex Payload Types Through an IJobRegistration<TJob> interface

[DCarlson12]

The JobRegistration.Create<TJob, THandler> strategy for supporting jobs with types not supported by default seems like a misfit in the source-generated strategy. Could registration not be handled by introducing an IJobRegistration<TJob> interface that carries the JsonTypeInfo<TJob> in it and the source generator could utilize that to create the JobRegistration? The narrow scope of permissible default payload types seems quite heavy-handed and introduces unnecessary friction. I’d be hard pressed to believe that the use of non-default types and collections are deemed an exception rather than an overwhelmingly standard rule in payload shapes. This seems like pre-optimization in the face of utility.

[pdevito3]

This is fair. I'm going to think on some paths forward here. Thanks for the callout!