fix(release): bump the embedded Windows version resource to 1.2.0

nebula.rc hardcodes FILEVERSION / PRODUCTVERSION and the two string
values; `chore(release): prepare v1.2.0` bumped every Cargo.toml but not
this file. The 1.2.0 package therefore shipped an exe whose Windows
properties, shortcut metadata and add/remove-programs entry all still
read 1.1.0 — only the installer itself carried the new number, because
the .ps1 sets that separately.

`--version` was correct throughout (build.rs derives it from
CARGO_PKG_VERSION), which is why the mismatch was invisible from the
command line.

Worth generating this file from CARGO_PKG_VERSION at build time so the
next release cannot drift the same way.

nebula_app/windows/nebula.rc

@@ -8,8 +8,8 @@ IDI_ICON ICON "nebula.ico"
 APP_MANIFEST RT_MANIFEST nebula.manifest
 
 1 VERSIONINFO
-FILEVERSION 1,1,0,0
-PRODUCTVERSION 1,1,0,0
+FILEVERSION 1,2,0,0
+PRODUCTVERSION 1,2,0,0
 FILEFLAGSMASK 0x3fL
 FILEFLAGS 0x0L
 FILEOS 0x40004L
@@ -22,11 +22,11 @@ BEGIN
         BEGIN
             VALUE "CompanyName", "Kuddev"
             VALUE "FileDescription", "Nebula Terminal"
-            VALUE "FileVersion", "1.1.0"
+            VALUE "FileVersion", "1.2.0"
             VALUE "InternalName", "nebula"
             VALUE "OriginalFilename", "nebula.exe"
             VALUE "ProductName", "Nebula Terminal"
-            VALUE "ProductVersion", "1.1.0"
+            VALUE "ProductVersion", "1.2.0"
         END
     END
     BLOCK "VarFileInfo"