[BUG] Unable to add a block-type disk with a new name

[derekbit]

Describe the bug (🐛 if you encounter this issue)

If a block-type disk was added and removed, the disk cannot be added to node with a new name.

To Reproduce

1. Add a block-type disk disk-1
2. Remove the disk
3. Add the block-type disk with a new name disk-2

Expected behavior

Support bundle for troubleshooting

Environment

• Longhorn version: v1.5.1 and master
• Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
• Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:
  • Number of management node in the cluster:
  • Number of worker node in the cluster:
• Node config
  • OS type and version:
  • Kernel version:
  • CPU per node:
  • Memory per node:
  • Disk type(e.g. SSD/NVMe/HDD):
  • Network bandwidth between the nodes:
• Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
• Number of Longhorn volumes in the cluster:
• Impacted Longhorn resources:
  • Volume names:

Additional context

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

#6849 (comment)

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Does the PR include the explanation for the fix or the feature?

• Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
  The PR is at

longhorn/longhorn-spdk-engine#65
longhorn/longhorn-instance-manager#296
longhorn/longhorn-manager#2202

• Which areas/issues this PR might have potential impacts on?
  Area: v2 volume, block-type disk
  Issues

[chriscchien]

Verified pass on longhorn master (longhorn-manager 396605)

1. Remove a block disk, then add that block disk again with a new name was successful.
2. After completing step 1, create a workload with V2 engine, that workload worked properly