Fix resolution with `default-features = false`

[alexcrichton]

There was previously a bug in resolve where turning off the default set of
features would cause resolve to not correctly settle on the set of features
activated for a package. If one dependency turned off all features, and then the
next dependency to be activated only turned on the default feature, the default
feature wouldn't actually end up getting activated.

This commit alters the check to see if the package has been previously activated
to more rigorously check to see if the 'default' feature is activated
previously. If a dependency doesn't use the default feature, or if the package
itself does not have the feature "default", then the package is considered
activated, but otherwise it needs to go through another cycle of resolution.

[rust-highfive]

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

[alexcrichton]

Reported here: http://www.reddit.com/r/rust/comments/39sq4t/dependency_is_recompiled_every_time_i_run_cargo/

[huonw]

@bors r+

[bors]

📌 Commit 0ba5a7a has been approved by huonw

[bors]

⌛️ Testing commit 0ba5a7a with merge 47735b1...

[bors]

☀️ Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64