Go through tryo usages, see if they are as far in as possible

[fm3]

Some of our own code is wrapped in tryo. We should go through the usages and see what exceptions this is about, and if the tryo can be moved further in, wrapping third-party code only.

Also, in the wake of this, it may be worth introducing the shortcut Fox.tryo, which turns the box into a fox directly.

[fm3]

I went through the 51 usages. Here are the ones that seem not ideal, where the tryo could be moved further in to make the caught exceptions more explicit:

• around VolumeBucketCompression.decompressIfNeeded (cannot be easily made to return a box because of iterator usage elsewhere)
• chunkTyper.wrapAndType
• BytesConverter.toByteArray
• dataExtractor.readBytesAndHeader
• N5ChunkReader.processBytes
• parseMinishardIndex
• BinaryDataService.convertIfNecessary
• UploadService.addLayerAndResolutionDirIfMissing