Investigate if cargo dependencies of type 'build' should be considered dev dependencies

Nobody has claimed this yet.

Today the detector when is inspecting the `kind` property of the dependency is only flagging it as dev dependency if `kind=dev` (see [here](https://github.com/microsoft/component-detection/blob/255e01115700899c5d5ea2cc82d1c3a40e68d315/src/Microsoft.ComponentDetection.Detectors/rust/RustCliDetector.cs#L243)), but other value that `kind` can have is `build`. These are dependencies used by the build script and probably should not be considered as dependencies of the final artifact.

- https://stackoverflow.com/questions/72861807/what-are-build-dependencies
- https://doc.rust-lang.org/cargo/reference/build-scripts.html

Start in src/Microsoft.ComponentDetection.Detectors/rust/RustCliDetector.cs around line 243, then read the linked Cargo build-script documentation to understand how `kind=build` dependencies differ from `kind=dev`. Done means establishing the expected classification for build dependencies and documenting or implementing that behavior in the Rust detector.

Written by the indexing model from the issue text.