Send the specific JetBrains IDE name for session tracking

Client-side follow-up from the [Scalable Approach for Adding New IDE Session Types RFC]() (lower priority than coder/vscode-coder#1044 since JetBrains IDEs are one vendor rather than many forks).

The plugin hardcodes `--usage-app=jetbrains` and `CODER_SSH_SESSION_TYPE=JetBrains` (`CoderCLIManager.kt`), and server-side process detection cannot tell PyCharm from GoLand, so every JetBrains IDE buckets under `jetbrains`.

Once the server accepts arbitrary app names (coder/coder#27410 → coder/coder#27412):

* Derive the product from the JetBrains platform API (e.g. `ApplicationInfo`/`ApplicationNamesInfo` product name) and send it through both mechanisms, e.g. `goland`, `pycharm`, `rustrover`; the server normalizes whatever is sent (lowercase, `-` → `_`)
* Same version-gating pattern as the VS Code extension: send a specific name only when the connected deployment is new enough, otherwise keep `jetbrains`
* Server-side family grouping keeps all of these under the JetBrains family in metric labels and legacy aggregates, so existing dashboards do not fragment

### Done when

- [ ] GoLand and PyCharm sessions are distinguishable in session counts on a new-enough deployment
- [ ] Older deployments still receive `jetbrains`

---

🤖 Created by Coder Agents on behalf of @EhabY.

Inizia da CoderCLIManager.kt e analizza le API della piattaforma JetBrains menzionate nell'issue, come ApplicationInfo o ApplicationNamesInfo, per il nome del prodotto. Confronta il pattern di version-gating dell'estensione VS Code e traccia entrambi i meccanismi di monitoraggio delle sessioni. Il lavoro è completato quando GoLand e PyCharm sono distinguibili nei nuovi deployment, mentre i deployment più vecchi continuano a ricevere jetbrains.

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