Use versioning for TrackMatcher types

[pb866]

Description

Use a version or format entry in the metadata of TrackMatcher types and allow graceful upgrades for older versions, where possible. This should be handled similarly to inventory versions in ICARE. Thus, when saving data, the version should be saved with it and when reloading data, different versions should be loaded without errors.

Acceptance Criteria

• A format version is saved for all TrackMatcher types that are saved for later processing.
  • FlightSet
  • FlightData
  • CloudData
  • SatData
  • CLay
  • CPro
  • Intersection
• When loading data, older versions can be recovered and upgraded gracefully.
• Versioning follows SemVer
• Versions are documented in the Documenter docs or a follow-up ticket is created

Definition of Done

• All ACs fulfilled
• Feature tested (unit tests written for new features or bugs)
• Documentation updated
  • in-code comments and docstrings
  • Documenter pages
  • Changelog was updated and docs were build
• The Git workflow was followed
  • Branches and PRs are linked to this ticket
  • A PR was made and reviewed for any new code
  • All CI checks passed
  • Related feature branch(es) merged and deleted without conflict