Ignore unresolved dependencies

Commands affecting containers in isolation should not fail because of missing/cyclic dependencies when attempting to ordering them if explicit order is missing. Typical use-case is to pipe the output of `crane status` limited to a certain group (that might have unresolved dependencies) in a script.
I don't think so, to me these 2 flags are really orthogonal (see title of a589000f82e0568c29261bdb22899da841180827). There could be cases where we want to make sure all reverse dependencies are in scope, and despite the signature of the method, that would be impossible if we use `reversed || ignoreUnresolved` here. I don't have strong opinion about this though, your call.