message: Fix resolve error with cyclic dev-dependency features.
  There is a convoluted situation where a cyclic dev-dependency attempts
  to enable a feature on its parent. It would result in a confusing error
  saying a package didn't have a feature.
  This check was intended only for CLI features, not features passed
  through the dependency graph.
diff: @@ -280,12 +280,14 @@ pub fn resolve_features<'b>(
  // dep_name/feat_name` where `dep_name` does not exist. All other
  // validation is done either in `build_requirements` or
  // `build_feature_map`.
  + if parent.is_none() {
  for dep_name in reqs.deps.keys() {
  if !valid_dep_names.contains(dep_name) {
  let e = RequirementError::MissingDependency(*dep_name);
  return Err(e.into_activate_error(parent, s));
  }
  }
  + }
  Ok((reqs.into_features(), ret))
  }
  