Update port selector range (microsoft#184689)

`registerPortAttributesProvider({portRange:[5000,5000]}...` doesn't match port 5000
Fixes microsoft#183846

Author: alexr00

src/vs/workbench/api/browser/mainThreadTunnelService.ts

@@ -83,7 +83,7 @@ export class MainThreadTunnelService extends Disposable implements MainThreadTun
 		// Check all the selectors to make sure it's worth going to the extension host.
 		const appropriateHandles = Array.from(this.portsAttributesProviders.entries()).filter(entry => {
 			const selector = entry[1];
-			const portRange = selector.portRange;
+			const portRange = (typeof selector.portRange === 'number') ? [selector.portRange, selector.portRange + 1] : selector.portRange;
 			const portInRange = portRange ? ports.some(port => portRange[0] <= port && port < portRange[1]) : true;
 			const commandMatches = !selector.commandPattern || (commandLine && (commandLine.match(selector.commandPattern)));
 			return portInRange && commandMatches;

src/vs/workbench/api/common/extHost.protocol.ts

@@ -1424,7 +1424,7 @@ export enum CandidatePortSource {
 }
 
 export interface PortAttributesSelector {
-	portRange?: [number, number];
+	portRange?: [number, number] | number;
 	commandPattern?: RegExp;
 }
 

src/vscode-dts/vscode.proposed.portsAttributes.d.ts

@@ -72,8 +72,9 @@ declare module 'vscode' {
 	export interface PortAttributesSelector {
 		/**
 		 * Specifying a port range will cause your provider to only be called for ports within the range.
+		 * The start is inclusive and the end is exclusive.
 		 */
-		portRange?: [number, number];
+		portRange?: [number, number] | number;
 
 		/**
 		 * Specifying a command pattern will cause your provider to only be called for processes whose command line matches the pattern.