Follow-up from "Skykey deletion"
The following discussions from !4634 (merged) should be addressed:
F/U: should switch these for alphabetization
If we break this check in two we will be able to exit early in case we find the key with this ID and realize that it's deleted. There is no reason to continue reading through the file.
This assumes that there can't be two keys with the same ID or one key entered twice in the manager.
F/U restructure this into multiple subtests. It's not ideal to have a single test for all skykey related endpoints and functionality. Instead we probably want a
testSkyKeywhich in turn calls
testSkyKeyDeleteand so on. In the output it should probably look like this