Shard lease did not release held leases cleanly when downed

[Arkatufus]

Version Information
Version of Akka.NET? 1.5.30
Which Akka.NET Modules? Akka.Sharding, Akka.Coordination

Describe the bug
Shard lease did not release held leases cleanly when downed, causing the same shard to fail to acquire the same lease when it is restarted.

This happens both in the Kubernetes and Azure Lease implementation, leaving a strong impression that Akka.Sharding Shard did not release the Lease it held properly when downed.

Kubernetes logs:

Azure logs:

The difference between k8s and Az is that, using k8s lease, the problem apparently heals itself quite fast while it lingers in Az.

Difference between k8s and az defaults:

akka.coordination.lease.kubernetes.lease-operation-timeout = 5s
akka.coordination.lease.azure.lease-operation-timeout = 15s

akka.coordination.lease.kubernetes.api-service-request-timeout = 2s
akka.coordination.lease.azure.api-service-request-timeout = 6s

[Arkatufus]

During termination, lease release operation was not being awaited properly, so there is a chance that a lease might not be released properly.