Add uniqueIdentifier to Storage

[grantfitzsimmons]

Is your feature request related to a problem? Please describe.
Storage locations are identified inconsistently, leading to human error when assigning a storage location for preparations and when handling movements from one location to another.

Describe the solution you'd like
We need to add a uniqueIdentifier field to the storage table. This uniqueIdentifier should be manually assigned rather than auto-generated, allowing us to uniquely identify storage locations. This will help ensure that all locations are globally uniquely identified, facilitating accurate and error-free movement of preparations.

There should be a uniqueness rule to make sure this is unique.

Describe alternatives you've considered
One alternative could be to continue using a combination of existing identifiers or repurposing a text field, but this may lead to inconsistencies and increased potential for human error. Another option could be to auto-generate uniqueIdentifiers, but we prefer manual assignment for better control and tracking. These uniqueIdentifiers are likely to be barcodes assigned using an external system, but it should be customizable so that field formats can be used in the application if necessary.

Reported By
KU Mammals, Birds, and Herpetology, requested formally by @zzeppozz

Additional context
We are currently conducting regular meetings with KU Mammals, Birds, and Herpetology to discuss this enhancement and its implications for our workflow, and this will likely be used as an important part of a later mechanism to move preparations from one location to another simply by entering the starting uniqueIdentifier (using a barcode scanner) and ending uniqueIdentifier in the interface.