Fix: Do not used closing terminals to spawn bitbake commands

If multiple commands where started at the same time, and we closed a
terminal that was still waiting for the bitbake lock, it could have
been reused.

client/src/ui/BitbakeTerminal.ts

@@ -72,12 +72,12 @@ export class BitbakePseudoTerminal implements vscode.Pseudoterminal {
   }
 
   async close (): Promise<void> {
+    if (!this.isTaskTerminal()) { bitbakeTerminals.splice(bitbakeTerminals.indexOf(this.parentTerminal as BitbakeTerminal), 1) }
     if (this.isBusy()) {
       // Wait for this process to be the one executed by bitbakeDriver
       await this.process
       void this.bitbakeDriver.killBitbake()
     }
-    if (!this.isTaskTerminal()) { bitbakeTerminals.splice(bitbakeTerminals.indexOf(this.parentTerminal as BitbakeTerminal), 1) }
   }
 
   handleInput (data: string): void {