Fix duplicate windows-sys versions and enforce in CI

[wmmc88]

This PR also seems to introduce 2 different versions of windows-sys into the build. This is not ideal for build times etc, but we can push that fix to a followup to unblock pipelines rn. It should just involving determining what's bringing in the duplicate versions and trying to uses cargo update to target an update to one. It might involve submitting a pr to loosen windows-sys version in a dependency, but i doubt that would be needed in this case since there are no new deps introduced in this pr.

Not sure why clippy isn't catching the duplicate though since we should already have https://rust-lang.github.io/rust-clippy/master/index.html#multiple_crate_versions enabled

Originally posted by @wmmc88 in #492 (review)

[wmmc88]

This looks to be because the newer version of tracing-subscriber causes an ancient version of windows-sys to be pulled in. Going to need to see if we can widen some ranges in other dependencies, or otherwise disable the tracing-subscriber ansi feature

[wmmc88]

I've widened the range in nu-ansi-term: nushell/nu-ansi-term#69

Just waiting for a release and then need to pull it in to tracing-subscriber

[wmmc88]

Tracking in tracing-subscriber: tokio-rs/tracing#3376

[wmmc88]

Tracking in tracing-subscriber: tokio-rs/tracing#3376

No change needed: #500 (comment)

[wmmc88]

Not sure why clippy isn't catching the duplicate though since we should already have https://rust-lang.github.io/rust-clippy/master/index.html#multiple_crate_versions enabled

Okay this was happening because the analysis for the lint happens per package, and there is not a single package in the workspace that will pull in to different versions (build deps and dev deps dont count since rust-lang/rust-clippy#5041 was resolved)