src/utils/pathUtils: adjust snap go path

A snapd issue prevents vscode-go (or node.js processes) from running
the symlinked /snap/bin/go binary reliably. Use /snap/go/current/bin/go
as suggested by users.

Fixes golang/vscdoe-go#166

Change-Id: I2231b439ea5403fd748ed2dd982a26437483c63d
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/545915
Auto-Submit: Hyang-Ah Hana Kim <[email protected]>
Reviewed-by: Alan Donovan <[email protected]>
Commit-Queue: Hyang-Ah Hana Kim <[email protected]>
Run-TryBot: Hyang-Ah Hana Kim <[email protected]>
TryBot-Result: kokoro <[email protected]>

Author: hyangah

src/utils/pathUtils.ts

@@ -102,8 +102,14 @@ export function getBinPathWithPreferredGopathGorootWithExplanation(
 	}
 
 	// Finally search PATH parts
-	const pathFromPath = getBinPathFromEnvVar(binname, getEnvPath(), false);
+	let pathFromPath = getBinPathFromEnvVar(binname, getEnvPath(), false);
 	if (pathFromPath) {
+		if (toolName === 'go' && pathFromPath === '/snap/bin/go') {
+			// Workaround for the snapd issue (golang/vscode-go#166)
+			// https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1849753
+			console.log('using /snap/go/current/bin/go instead of /snap/bin/go (see golang/vscode-go#166)');
+			pathFromPath = '/snap/go/current/bin/go';
+		}
 		binPathCache[toolName] = pathFromPath;
 		return { binPath: pathFromPath, why: found('path') };
 	}