Cargo should strip features of dev dependencies

[Morganamilo]

Problem

#7333 added stripping of dependencies, but did not strip features pointing to those dependencies.

This causes a rather unintuitive error where cargo says the dependency does not exist. Which one would only understand if they knew about the stripping that cargo does.

Proposed Solution

Cargo should also strip these features from the manifest before publishing.

If foo is a dev-dependency being stripping then a = ["foo/a"] should be transformed to a = [].

Notes

No response

[eval-exec]

@rustbot claim

[eval-exec]

Hello, I submitted a PR to fix this。 Would you like review my PR and provide your feedback? 💟