Make init extension command use current file

This patch makes `init the exstension` command use the current file to
determine the matching root folder.

For instance you have this hierarchy.

```
workspace
- proj1
- proj2
  - file.txt
```

Previously the extension only created the LSP configuration file in
`proj1` dir. Now if you open `file.txt` in `proj2` and run `init the
extension`, it will create the configuration file in `proj2` dir.

Author: georgiy-belyanin

CHANGELOG.md

@@ -22,6 +22,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Now the id is `tarantool` instead of `tarantool-vscode` and the package name
   is simple `Tarantool`.
 - Tarantool annotations aren't longer used as a submodule.
+- Now initialize the extension command also tries to initialize the extension
+  in the workspace folder in which the opened file is located.
 
 ### Fixed
 

src/extension.ts

@@ -13,10 +13,18 @@ const emmyrc = {
 };
 
 async function initVs() {
+	const file = vscode.window.activeTextEditor?.document.uri.fsPath;
+
 	const wsedit = new vscode.WorkspaceEdit();
-	const wsPath = vscode.workspace.workspaceFolders?.at(0)?.uri.fsPath;
+	const wsFolders = vscode.workspace.workspaceFolders?.map((folder) => folder.uri.fsPath);
+	if (!wsFolders) {
+		vscode.window.showWarningMessage('Please, open a project before running this command');
+		return;
+	}
+	
+	const wsPath = file ? wsFolders.find((folder) => file.startsWith(folder)) : wsFolders.at(0);
 	if (!wsPath) {
-		vscode.window.showWarningMessage('Please, open project before running this command');
+		vscode.window.showWarningMessage('Please, open at least one folder within the workspace');
 		return;
 	}