Restrict existing packages depending on mirage-crypto to < 1.0.0
The reasoning is that soon there'll be a mirage-crypto 1.0.0 release which has
major breaking changes: Cstruct/bigarray is no longer being used, instead
string/bytes are used. Since this is not backward-compatible, let's put bounds
on everything and get new releases out rather sooner than later :)