tacd: update dependencies via cargo update

[hnez]

A routine update inspired by #80. It does not get rid of the security advisory though.

[Emantor]

We gain windows-sys which according to the crate information is used for Windows APIs. We don't have those, so I suspect this can be disabled through explicit feature specification.

[hnez]

We gain windows-sys …

*yet another version of windows-sys:

tacd/Cargo.lock

Lines 3151 to 3176 in b245e39

	[[package]]
	name = "windows-sys"
	version = "0.48.0"
	source = "registry+https://github.com/rust-lang/crates.io-index"
	checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
	dependencies = [
	"windows-targets 0.48.5",
	]
	[[package]]
	name = "windows-sys"
	version = "0.52.0"
	source = "registry+https://github.com/rust-lang/crates.io-index"
	checksum = "282be5f36a8ce781fad8c8ae18fa3f9beff57ec1b52cb3de0789201425d9a33d"
	dependencies = [
	"windows-targets 0.52.6",
	]
	[[package]]
	name = "windows-sys"
	version = "0.59.0"
	source = "registry+https://github.com/rust-lang/crates.io-index"
	checksum = "1e38bc4d79ed67fd075bcc251a1c39b32a1776bbe92e5bef1f0bf1f8c531853b"
	dependencies = [
	"windows-targets 0.52.6",
	]

As far as I can tell the Cargo.lock lists the hashes of any package that may be used in any possible build scenario.
I do not know if feature flags set in the Cargo.tomlaffect it that much.

I think most important for us is that none of the windows-sys versions listed in the Cargo.lock are actually compiled when the tacd is built.

[Emantor]

Ah, TIL. Apparently Cargo.lock always contains all build deps so it stays consistent across platforms which makes sense to me.

[hnez]

Hi @Emantor, now that the windows-sys questions are resolved, could you give this an approval?
I already have the next set of updates in the pipeline with #84.

[hnez]

I was about to just merge this myself, but it turns out I do not have permissions to do that.
Soo @KarlK90 or @Emantor, can I get an approval please?