Document per-file interpreter resolution in the config middleware

Clarify why the workspace/configuration handler resolves the interpreter for the exact .py file (exactResource) rather than its folder: it honors a per-file environment such as a PEP 723 inline-script env for the language client this extension hosts, and only diverges from folder resolution when the Python Environments extension is in use.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Copilot

src/client/activation/languageClientMiddlewareBase.ts

@@ -87,6 +87,11 @@ export class LanguageClientMiddlewareBase implements Middleware {
                     const settingDict: LSPObject & { pythonPath: string; _envPYTHONPATH: string } = settings[
                         i
                     ] as LSPObject & { pythonPath: string; _envPYTHONPATH: string };
+                    // For a .py file resource, resolve the interpreter for that exact file rather than its
+                    // containing workspace folder, so a per-file environment (such as a PEP 723 inline-script
+                    // environment created for a single script) is honored for the language client hosted by
+                    // this extension. This only diverges from workspace-folder resolution when the Python
+                    // Environments extension is in use; otherwise getActiveInterpreter ignores exactResource.
                     const exactResource = uri && path.extname(uri.fsPath).toLowerCase() === '.py';
                     settingDict.pythonPath =
                         (