Add Azure Event Hubs component

[ReubenBond]

We should add an Azure Event Hubs component.
We identified this in the Orleans component PR (#1117), since many Orleans users use Azure Event Hubs for stream processing.

[davidfowl]

I wrote an event hubs sample here (no component but an azure resource):

• https://github.com/davidfowl/AspireEventHub

[oising]

@davidfowl helped me get started this weekend on getting his example integrated into the latest bits, so if you want to assign me, I'm giving it a shot. /cc @ReubenBond

[ReubenBond]

Greatly appreciated, @oising! We're here to help if you run into trouble

[jsquire]

@davidfowl helped me get started this weekend on getting his example integrated into the latest bits, so if you want to assign me, I'm giving it a shot. /cc @ReubenBond

@oising : One thing that I'll mention about David's prototype is that you definitely don't want to use the consumer's ReadEventsAsync for production scenarios unless you've got a very low volume. As noted in the docs, that method is intended to provide an easy "Hello World" experience for exploring Event Hubs. It doesn't provide any fairness guarantees when reading from partitions, does not scale well with a large number of partitions, nor perform under load.

Depending on whether the intention is to allow for multiple instances to be running in the app or a single instance, we'd want to look at PluggableCheckpointStoreEventProcessor<T> or PartitionReceiver.

[oising]

@jsquire This brings up another somewhat orthogonal point. I've yet to read anything about Aspire being aimed at production scenarios (though I can absolutely imagine this, especially with something like Pulumi integrated) -- Aspire finds itself in a weird no-mans land here. It would be good to get messaging around this, because these choices (PartitionReceiver vs EventHubConsumer) are entwined with this vision.