any array with item count close to INT32_MAX would not fit LUKS2 header json area anyway
Originally the key description for VK was derived from segment id. This could lead to ambiguity when keyslot key is verified and loaded in kernel keyring using activation functions with CRYPT_ACTIVATE_KEYRING_KEY flag raised.
simplify crypt_drop_keyring_key also do not search for keyring keys when we know we haven't loaded any
