v0.14.0 — rename PSLauncher.exe → PS_Launcher.exe (with backward compat)

Aligns the executable name with the repo / product naming. Backward-
compatible: existing installs that have PSLauncher.exe on disk continue
to work — the self-updater overwrites the file at the running .exe path
without renaming, so the historical filename persists on those machines.

Changes
- AssemblyName : PSLauncher → PS_Launcher (both App and Updater csproj)
- Inno Setup : MyAppExeName, MyUpdaterExeName, OutputBaseFilename all
  now use PS_Launcher prefix
- LauncherSelfUpdater : looks for PS_Launcher.Updater.exe first, falls
  back to legacy PSLauncher.Updater.exe so old installs keep updating
- Build scripts (build-launcher / build-updater / build-installer /
  build-all) : taskkill both legacy AND new names; output paths printed
  with new names
- .gitignore : added PS_Launcher.exe / PS_Launcher.Updater.exe /
  PS_Launcher-*.exe patterns alongside the legacy ones; also ignored
  the WebView2 user-data folder and Office ~$ lock files
- Server admin/launcher.php : URL pattern now generates
  PS_Launcher-{ver}.exe ; SignManifest's existing tolerant glob
  *{ver}*.exe still matches both names
- Versions bumped to 0.14.0 (App + Updater + installer .iss)

Migration story for clients
- Brand-new install via PS_Launcher-Setup-0.14.0.exe → PS_Launcher.exe
  on disk
- Existing install (PSLauncher.exe) auto-updates to v0.14 → file stays
  named PSLauncher.exe but contains v0.14 code; self-updater fallback
  ensures future updates keep working

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

installer/PSLauncher.iss

@@ -4,18 +4,22 @@
 ;   "C:\Program Files (x86)\Inno Setup 6\ISCC.exe" PSLauncher.iss
 ;
 ; Avant compile :
-;   1. Faire `dotnet publish src/PSLauncher.App      -c Release` (génère PSLauncher.exe ~77 Mo)
-;   2. Faire `dotnet publish src/PSLauncher.Updater  -c Release` (génère PSLauncher.Updater.exe ~10 Mo)
+;   1. Faire `dotnet publish src/PSLauncher.App      -c Release` (génère PS_Launcher.exe ~77 Mo)
+;   2. Faire `dotnet publish src/PSLauncher.Updater  -c Release` (génère PS_Launcher.Updater.exe ~10 Mo)
 ;
 ; Le script picore directement les binaires dans bin/Release/.../publish/.
 
 #define MyAppName        "PROSERVE Launcher"
-#define MyAppShortName   "PSLauncher"
-#define MyAppVersion     "0.13.0"
+#define MyAppShortName   "PS_Launcher"
+#define MyAppVersion     "0.14.0"
 #define MyAppPublisher   "ASTERION VR"
 #define MyAppURL         "https://asterionvr.com"
-#define MyAppExeName     "PSLauncher.exe"
-#define MyUpdaterExeName "PSLauncher.Updater.exe"
+; Renommé en v0.14.0 (PSLauncher.exe → PS_Launcher.exe). Les nouvelles installs
+; auront ce nom ; les anciennes installs auto-updatées garderont PSLauncher.exe
+; sur disque (le self-updater écrase le fichier sans le renommer). Code OK pour
+; les deux variantes.
+#define MyAppExeName     "PS_Launcher.exe"
+#define MyUpdaterExeName "PS_Launcher.Updater.exe"
 
 [Setup]
 ; AppId est UNIQUE pour PSLauncher — ne pas changer entre deux versions sinon
@@ -29,12 +33,12 @@ AppPublisherURL={#MyAppURL}
 AppSupportURL={#MyAppURL}
 AppUpdatesURL={#MyAppURL}
 ; Installation user-mode (pas d'admin requis) : le launcher pourra se mettre à jour
-; tout seul via PSLauncher.Updater.exe sans déclencher de UAC.
+; tout seul via PS_Launcher.Updater.exe sans déclencher de UAC.
 DefaultDirName={localappdata}\Programs\{#MyAppPublisher}\{#MyAppShortName}
 DefaultGroupName={#MyAppName}
 DisableProgramGroupPage=yes
 OutputDir=output
-OutputBaseFilename=PSLauncher-Setup-{#MyAppVersion}
+OutputBaseFilename=PS_Launcher-Setup-{#MyAppVersion}
 SetupIconFile=..\src\PSLauncher.App\Resources\favicon.ico
 Compression=lzma2/ultra
 SolidCompression=yes