feat(gradle): analyze a Gradle project's dependencies per configuration (#1181)

The Dependency Analyzer lists Gradle projects next to Maven modules. For a Gradle project it runs `<project>:dependencies --configuration <name>` (compile/runtime/test classpaths) in the background (on the project host for remote projects), cancellable and cached per session, and reuses the list/tree views, search, conflicts-only filter and usage paths: an exact request Gradle replaced (1.0 -> 1.1) is a conflict showing the requested version, constraints are left out, unresolved dependencies are marked and build projects (quoted or not) are recognised. Exclude / Jump to Source stay Maven-only. Opened from the Gradle tool window toolbar, a Gradle project's context menu and a build script's menus.

Closes #1005

src-tauri/src/commands/build.rs

@@ -43,6 +43,21 @@ pub async fn build_sync(
     .await
 }
 
+/// The resolved dependency tree of a Gradle project for one configuration (Dependency Analyzer).
+#[tauri::command]
+#[specta::specta]
+pub async fn gradle_dependencies(
+    window: Window,
+    state: State<'_, AppState>,
+    gradle_path: String,
+    configuration: String,
+    offline: bool,
+    request: RequestId,
+) -> IdeResult<Vec<ide_build::GradleDependency>> {
+    ide_host::ops::build::gradle_dependencies(&state.host, window.label(), gradle_path, configuration, offline, request)
+        .await
+}
+
 /// The `.toml` of a version catalog the build imports as `group:artifact:version`, once a
 /// build has downloaded it.
 #[tauri::command]

src-tauri/src/commands/mod.rs

@@ -340,6 +340,7 @@ pub fn builder() -> tauri_specta::Builder<tauri::Wry> {
         run::run_test_reports,
         build::build_model,
         build::build_sync,
+        build::gradle_dependencies,
         build::gradle_published_catalog,
         build::maven_dependency_declaration,
         build::maven_exclude_dependency,