Versioning

As this app is becoming more mature and is being used in projects, we should consider a versioning scheme with tagged versions, even if we push to https://app.giro3d.org via continuous deployment. This would greatly help communication regarding updates.

Proposal

• Calendar-based releases, every quarter: January, April, July and October, second Tuesday of the month - e.g. April 9th, July 9th, October 8th, January 14th 2025, etc.
• Version number based on Calendar, e.g. v24.4 for April 2024 release, v24.7 for July 2024, v24.10 for October 2024, v25.1 for January 2025, etc.
• Not using semver, as the notion of breaking changes is hard to define properly
  • However some breaking changes are "easy" to identify, e.g. those that require "manual" changes from integrators: changes in the configuration format (src/config.ts, src/styles.ts) or the build system
  • such changes should be clearly identified in the changelog
• The current version used to build the app is clearly identified in the About panel (done via !56 (merged))