[BUG] Naming collision when creating the name of the new backing image manager

[PhanLe1010]

Describe the Bug

The name of the backing image manager will be backing-image-manager-<first-4-characters-of-backing-image-checksum>-<first-4-characters-of-disk-uuid> : link code

This could cause naming collision for example when both of the backing image manager are having:

• Same first-4-characters-of-backing-image-checksum is SHA-512("longhornio/backing-image-manager:v1.7.2") which is 5ae6
• And same <first-4-characters-of-disk-uuid> is c4d3 . Even though the full disk UUIDs are different

As the consequence, the 2nd backing image manager can never be created so replica using that backing image can never be started

To Reproduce

Very rare. the chance of naming collision would be 1/36^4 which is around 0.00006%

Difficult to reproduce

Expected Behavior

Do not have naming collision

Support Bundle for Troubleshooting

NA

Environment

• Longhorn version: v1.7.2

Additional context

No response

Workaround and Mitigation

No response