Azure Event Hubs manifest should allow specifying InstanceID for faster partition lease recovery (pubsub/binding)

[oising]

Describe the feature

When consuming messages either via the PubSub or Bindings component with Event Hubs as a backing store, partitions are leased by the consuming client. This is because there is often a pool (i.e. a consumer group) that is operating with the competing consumer pattern. Each client (i.e. sidecar) must assert ownership in the group before it can read messages. This ownership is kept in a shared storage account. When the Azure Event Hubs Go consumer client starts up, it will generate a random InstanceID - see https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/messaging/azeventhubs#ConsumerClientOptions - to use as its "Owner ID" in metadata on the block blob that represents the claimed partition. Each time the client restarts though, the InstanceID is regenerated and the client needs to wait for the default timeout period (normally 2 mins) before it can reclaim the partition (because it is flagged as owned by the previous random uuid.)

See comments on the dotnet client:

The identifier can be set using the Identifier property on the EventProcessorClientOptions passed when constructing the processor. If not specified, a random identifier will be generated.

It is recommended that you set a stable unique identifier for processor instances, as this allows the processor to recover partition ownership when an application or host instance is restarted. It also aids readability in Azure SDK logs and allows for more easily correlating logs to a specific processor instance.

This greatly lengthens the recovery time for a partition to start feeding messages to a consuming app, and as such increases the development time for dapr developers.

Release Note

RELEASE NOTE: