Use the port number to find the func pid

[nturinski]

Reverts always terminating the func process introduced in this PR

I mentioned it in that PR, but if you kill the entire shell process, the terminal also gets deleted. I thought it wouldn't be that annoying, but there are times when your func process errors, and it just immediately disappears so it looks like the debug was a no-op.

I thought that there must be a better way and tried to find the real PID by looking for the port number instead. This seems to work quite a bit better.

Mac testers would be greatly appreciated.

[Copilot]

Pull Request Overview

This PR reverts a previous change that always terminated the entire shell process when stopping func tasks, and implements a more targeted approach by finding the actual func process PID using port number lookup. The key motivation is to prevent terminals from being deleted when func processes error, which was causing debug sessions to appear as no-ops.

Key changes:

• Replaces shell process termination with port-based PID lookup for killing func processes
• Adds platform-specific implementations for finding processes by port (Windows netstat/PowerShell, Linux/Mac lsof)
• Updates function signatures to be async where needed

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
src/funcCoreTools/funcHostTask.ts	Implements the core logic for finding and killing func processes by port, with fallback mechanisms
src/commands/pickFuncProcess.ts	Updates call to use the new async stopFuncTaskIfRunning function