Fix Launch4j version metadata format breaking Windows packaging in build-and-release

[Copilot]

The build-and-release workflow failed in the Windows packaging step because Launch4j generated an invalid RC FILEVERSION from the date-based project version (2026.08.04.1). windres rejects zero-padded numeric segments like 08/04 in that context.

• Root cause

  • CimPal-Main Launch4j config mapped ${cimpal.version} directly into numeric version fields:
    • <fileVersion>
    • <productVersion>
  • This produced invalid RC numeric literals for windres.

• Change made

  • Updated Launch4j numeric version fields in CimPal-Main/pom.xml to use a windres-safe numeric format (no zero-padded date segments) for:
    • fileVersion
    • productVersion
  • Kept string version fields unchanged for display/metadata continuity:
    • txtFileVersion
    • txtProductVersion

• Why this is safe

  • Change is isolated to Windows executable metadata generation in Launch4j.
  • No runtime application logic or dependency behavior is altered.

<versionInfo>
  <fileVersion>2026,8,4,1</fileVersion>          <!-- numeric, windres-safe -->
  <txtFileVersion>${cimpal.version}</txtFileVersion>
  <productVersion>2026,8,4,1</productVersion>    <!-- numeric, windres-safe -->
  <txtProductVersion>${cimpal.version}</txtProductVersion>
</versionInfo>