Fix default features in dependency

[gui1117]

If in a crate Cargo.toml there is a dependency with default-features = true and workspace = true
If in the workspace Cargo.toml the depended crate is written with default-features = false

Then we must serialize the default-features = true when doing the manifest for the test.

Otherwise the test will run with default-features = false which is not the expected behavior.

[dtolnay]

Thanks!

[gui1117]

Thank you for the crate

[Guiguiprim]

Hello !

I think there is an issue with this.

My Cargo.toml only contains workspace = true (no default-features), but the workspace Cargo.toml does contains default-features = false.
As far as I understand if the field is not present it defaults as true, so with this change we wrongly set default-features = true.

Extract from my use case:

[dependencies.ed25519-compact]
default-features = true
workspace = true

[workspace.dependencies.ed25519-compact]
version = "2.1.1"
default-features = false
features = ["std", "x25519"]

In my setup, the CI use --locked --offline when running the tests (crates are fetch in a previous step) and as a result the build fails with missing ct-codecs (which came with the pem default feature).

[gui1117]

Indeed maybe default features should be an option of boolean.