partitionOwnershipExpirationInterval setting not applied

**Describe the bug**
We are using **spring-cloud-azure-starter-eventhubs** version 7.4.0. We have configured rebalancing and partition ownership expiration internal as per documentation:

```
spring:
cloud:
azure:
eventhubs:
processor:
load-balancing:
partition-ownership-expiration-interval: 30s
update-interval: 10s
```

We can clearly see in logs that load balancing is performed every 10s, as configured, but partition ownership is only re-assigned after the default 2 minutes. The configuration property is ignored.

**To Reproduce**
Create an eventhubs consumer with above configuration. It is sufficient to make it listen to a topic with only one partition configured. Then stop the pod/instance, at which point a new instance will automatically be started up. In the logs, it can be seen that the new instance performs load balancing every 10s, but only after 2 minutes it obtains ownership of the partition that was released by the earlier terminated listener.

**Expected behavior**
The new consumer should be granted ownership of the partition after 30s, as per configuration.

**Screenshots**
n/a

**Additional context**
n/a

**Can we contact you for additional details?**
Y

If yes, please send us your contact information to AzureSpringCloud-Talk@service.microsoft.com and include the issue number in the email title.

Beginne damit, die Spring Cloud Azure Event Hubs-Prozessorkonfiguration für partition-ownership-expiration-interval und deren Load-Balancing-Einrichtung nachzuverfolgen. Reproduziere dies mit einem Topic mit einer Partition, einem Ablaufintervall von 30 Sekunden und einer beendeten Instanz; abgeschlossen ist die Aufgabe, wenn der Ersatzconsumer nach etwa 30 Sekunden statt der standardmäßigen zwei Minuten die Ownership erhält.

Vom Indexierungsmodell aus dem Issue-Text verfasst.