features-import-all can fail for inter-dependent features

Let's say that you create two new features, one name foo that contains a field, and another named bar that contains a view that displays that field. Bar explicitly depends on foo. If you run features-import-all, it will fail with a cryptic exception, because it tries to import features in alphabetical order, leading it to try to import bar before foo.

features-import-all needs to build a dependency tree and make sure to import each feature in an order that ensures dependencies are met.