[FEATURE]: Modernize YAML configuration serialization strategy

[arturcic]

Summary

GitVersion should move away from the current YAML-processing approach to a modern, maintainable alternative that is compatible with current and future runtime scenarios.

Goal

Adopt a YAML serialization/deserialization approach that:

• supports source-generated metadata or an equivalent strategy that reduces runtime reflection requirements,
• keeps configuration parsing behavior stable for users,
• maintains compatibility with existing configuration files and naming conventions,
• improves long-term maintainability and reliability of configuration handling.

Success Criteria

• Configuration loading and merging behavior remains consistent from a user perspective.
• Existing configuration-focused tests continue to pass.
• The selected approach is suitable for modern runtime constraints (including AOT-related scenarios).

References

• Using the YamlDotNet source generator for NativeAOT

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs.