cargo.md and currentreleasenotes.md update for cargo cli detector

Author: zahidblackduck

documentation/src/main/markdown/currentreleasenotes.md

@@ -23,6 +23,9 @@
 ### New features
 
 * Support for Conda has been extended to 25.1.1.
+Here’s the revised line, following your requested format:
+* A new detector leveraging `cargo tree` to extract direct and transitive dependencies, improving accuracy over the previous flat-list detection. This build-based detector is triggered for Cargo projects with a `Cargo.toml` file and requires Cargo version **1.44.0+**. Falls back to the existing build-less approach if `cargo tree` is unavailable.  
+* Added property `detect.cargo.path` to allow users to specify a custom Cargo executable path.  
 
 ### Resolved issues
 

documentation/src/main/markdown/packagemgrs/cargo.md

@@ -1,11 +1,32 @@
 # Cargo support
 
-## Overview
+## Overview  
 
-[detect_product_short] runs the Cargo detector if it finds either of the following files in your project:
+[detect_product_short] now includes two Cargo detectors:
 
-* Cargo.toml
-* Cargo.lock
+* **Cargo CLI Detector** (New)  
+* **Cargo Lockfile Detector**  
 
-The Cargo detector parses the Cargo.lock file for information on your project's dependencies. If the detector discovers a Cargo.toml file but not a Cargo.lock file, it will prompt the user to generate a Cargo.lock by running `cargo generate-lockfile` and then run [detect_product_short] again.
-The Cargo detector extracts the project's name and version from the Cargo.toml file.  If it does not find a Cargo.toml file, it will defer to values derived by Git, from the project's directory, or defaults.
+## Cargo CLI Detector  
+
+A new cli detector for Cargo projects, which extracts **direct and transitive dependencies** using the `cargo tree` command. This improves the accuracy of dependency detection over the previous flat-list detection.
+
+**Requirements:**  
+* Cargo version **1.44.0+** is required (as `cargo tree` was introduced in this version).  
+* A `Cargo.toml` file must be present in the project.  
+* A valid `cargo` executable must be available on the system.
+
+**Behavior:**  
+* Executes `cargo tree` to analyze dependencies.  
+* Parses the output to construct a hierarchical **dependency graph**.  
+* Falls back to the Cargo Lockfile Detector if `cargo tree` is unavailable.
+
+To specify a custom Cargo executable path, use the `detect.cargo.path` property.  
+
+## Cargo Lockfile Detector  
+
+If `cargo tree` is unavailable, [detect_product_short] will default to the Cargo Lockfile Detector, which extracts dependencies by parsing the `Cargo.lock` file.
+
+* If both `Cargo.toml` and `Cargo.lock` are present, the detector uses `Cargo.lock` for dependency information.  
+* If `Cargo.lock` is missing, the detector prompts the user to generate it using `cargo generate-lockfile`.  
+* Extracts the project’s name and version from `Cargo.toml`. If missing, it derives values from Git or the project directory.