Forward unstable feature flags (-Z) to cargo metadata invocations

[rnza0u]

The problem

I ran across some issues when using nightly Cargo features such as artifacts-dependencies.

Cargo forces users to pass a -Z bindeps flag to activate the feature in every cargo command.

Cross already forwards the +nightly flag to internal cargo invocations, but it does not forward -Z flags.

Consequently, cargo metadata always fail for projects using such feature.

This problem would also occur when using other Cargo nightly features.

Solution

Parse the -Z flags and forward them to cargo metadata.