docs: document _getDependencyData() directory parameter semantics (#476)

* docs: document _getDependencyData() directory parameter semantics

Add JSDoc to Base_pyproject._getDependencyData() explaining that
manifestDir is the project directory and workspaceDir is the lock file
directory. Documents when each should be used by lock-file-based vs
non-lock-file providers.

Implements TC-4102

Assisted-by: Claude Code

* docs: address review feedback on _getDependencyData JSDoc

Remove caller reference, fix inaccurate fallback claim, and correct
workspaceDir description to scope it to uv only (poetry ignores it).

Implements TC-4102

Assisted-by: Claude Code

* docs: drop obvious JS convention from JSDoc

Implements TC-4102

Assisted-by: Claude Code

Author: ruromero

src/providers/base_pyproject.js

@@ -168,8 +168,10 @@ export default class Base_pyproject {
 
 	/**
 	 * Resolve dependencies using the tool-specific command and parser.
+	 *
 	 * @param {string} manifestDir - directory containing the target pyproject.toml
-	 * @param {string} workspaceDir - workspace root (where the lock file lives), or same as manifestDir for standalone projects
+	 * @param {string} workspaceDir - workspace root (where the lock file lives);
+	 *   only used by providers that need workspace-level resolution (e.g. uv)
 	 * @param {object} parsed - parsed pyproject.toml
 	 * @param {Object} opts
 	 * @returns {Promise<DependencyData>}