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>

src/PSLauncher.App/PSLauncher.App.csproj

@@ -10,14 +10,19 @@
     <LangVersion>latest</LangVersion>
     <ImplicitUsings>enable</ImplicitUsings>
     <ApplicationIcon>Resources\favicon.ico</ApplicationIcon>
-    <AssemblyName>PSLauncher</AssemblyName>
+    <!-- AssemblyName définit le nom du .exe en sortie. Renommé en v0.14.0 :
+         PSLauncher.exe → PS_Launcher.exe pour s'aligner sur le nom du repo
+         et du produit. Les anciens installs (qui ont PSLauncher.exe) gardent
+         leur nom de fichier après auto-update : le self-updater écrase le
+         fichier au path courant sans le renommer. Le code reste rétro-compatible. -->
+    <AssemblyName>PS_Launcher</AssemblyName>
     <Company>ASTERION VR</Company>
     <Product>PROSERVE Launcher</Product>
     <Copyright>© 2026 ASTERION VR — All rights reserved</Copyright>
     <RootNamespace>PSLauncher.App</RootNamespace>
-    <Version>0.13.0</Version>
-    <AssemblyVersion>0.13.0.0</AssemblyVersion>
-    <FileVersion>0.13.0.0</FileVersion>
+    <Version>0.14.0</Version>
+    <AssemblyVersion>0.14.0.0</AssemblyVersion>
+    <FileVersion>0.14.0.0</FileVersion>
 
     <!-- Single-file self-contained publish profile (used by `dotnet publish`) -->
     <PublishSingleFile>true</PublishSingleFile>
@@ -60,7 +65,7 @@
   </ItemGroup>
 
   <!-- Après chaque `dotnet publish -c Release`, copie le single-file exe à la racine du repo
-       (C:\ASTERION\GIT\PS_Launcher\PSLauncher.exe). ContinueOnError pour ne pas casser le
+       (C:\ASTERION\GIT\PS_Launcher\PS_Launcher.exe). ContinueOnError pour ne pas casser le
        publish si une instance du launcher tourne et verrouille la cible — l'opérateur peut
        killer et réessayer, ou simplement utiliser le binaire depuis bin\Release\... -->
   <Target Name="CopyPublishedToRepoRoot" AfterTargets="Publish"