[BUG][vscode-extension] Code Analyzer can't find SF CLI

### Bug Description

We have had multiple reports of users who have the Salesforce CLI installed receiving an error message informing them they do not have the CLI installed, such as: "To use the Salesforce Code Analyzer extension, first install Salesforce CLI."

This can occur for a few reasons, but the root cause is that `sf` is not appearing in the PATH of the running VS Code instance. This tends to affect mac users when you have installed outside of the [recommended](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm#sfdx_setup_install_cli_macos) CLI steps. We are currently looking into a fix for this.

### Steps To Reproduce

1. Open the Code Analyzer VS Code Extension
2. See an error message that the CLI is not installed, preventing use.

### Expected Behavior

If I have the SF CLI installed, Code Analyzer should be able to find it

### Operating System

All

### Visual Studio Code Version

Latest

### Extension Version

1.10.1

### Salesforce CLI Version

2.104.6

### Code Analyzer CLI Plugin Version

5.4.0

### Additional Context (Screenshots, Files, etc)

### Workaround

Open VS Code using the terminal to ensure the `sf` is located in the path of your VS Code application. Re-install the CLI using the [recommended](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm#sfdx_setup_install_cli_macos) steps. Do not use homebrew, or install SF with the assistance of `sudo`.

### Urgency

Moderate

Inizia riproducendo il problema seguendo i passaggi elencati e confronta VS Code avviato normalmente con VS Code avviato da un terminale. Analizza come l’estensione rileva la CLI `sf` installata, quindi verifica che una CLI installata venga trovata nella configurazione macOS interessata senza l’errore errato di CLI mancante.

Scritto dal modello di indicizzazione a partire dal testo della issue.