Fix auto-updater loop by removing hardcoded FileVersion and AssemblyVersion

[Copilot]

Auto-updater repeatedly offered updates from 0.2.0 to 0.4.0 because Updatum reads AssemblyVersion from the executable, which was hardcoded to 0.2.0 while semantic Version was 0.3.0.

Changes

• Remove hardcoded version properties from csproj files
  • Deleted <FileVersion>0.2.0</FileVersion>
  • Deleted <AssemblyVersion>0.2.0</AssemblyVersion>
  • Kept only <Version>0.3.0</Version>

When FileVersion and AssemblyVersion are unspecified, .NET automatically derives them from Version. Since CI already passes -p:Version={semVer} during builds, all three properties will now stay synchronized:

<!-- Before: versions out of sync -->
<Version>0.3.0</Version>
<FileVersion>0.2.0</FileVersion>
<AssemblyVersion>0.2.0</AssemblyVersion>

<!-- After: auto-derived from Version -->
<Version>0.3.0</Version>

When CI builds with -p:Version=0.4.0, the executable will correctly report 0.4.0 for all version properties.

Documentation

Added docs/VERSIONING.md explaining version management strategy and the relationship between GitVersion, csproj properties, and Updatum.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Auto updated keeps wanting to update</issue_title>
<issue_description>When the app restarts and the auto updater runs, it keeps wanting to update me from 0.2.0.0 to 0.4.0

I haven't dug into how the auto-updater is working, but it looks to be related to the version stamping on the exe as below.

</issue_description>

<agent_instructions>0.2.0.0 is asking for 0.4.0 over and over...why?</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@shanselman Checking! @demyte thanks for the report!

• Fixes Auto updated keeps wanting to update #16

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.