Major breaking changes tracking

Purpose

This issue will be an overview of planned changes that will be breaking to Strides core. This will allow us to consolidate discussions, PRs and issues into a single place for future planning.

Current PRs

• #2404 likely going to be closed in favour of #2574
• #2574 The main PR related to changing the core startup and surface rendering of Stride

Current Discussions

• #2524 The discussion related to strides startup changes
• #2210 Tracking for talks about changing to System.Numerics

Tasks

TBD I will fill this out better with breakdowns for what is needed to get going on the above discussions

Math

• Deprecate Stride math extensions in favour of System.Numerics
• Change core math types to the System.Numerics equivelent
• Add Implicit conversions to System.Numerics

Game startup

• Change to a more robust GameWindow
• decouple the GameWindow from GamePlatform maybe in favour of something that defines just the update/render loop?
• remove GameContext it serves no real purpose and just adds an unnecessary layer. Should use GameSettings instead
• remove cyclical dependencies between systems, discussed here
• Move Game.IsMouseVisible out of the GameWindow and into the Input library.

Graphics

• https://github.com/stride3d/stride/pull/2186

branch chores

• Make a new dedicated branch for proper testing (5.0?)

Start with PR #2574 and discussion #2524 to understand the proposed core startup and surface-rendering changes, then review the System.Numerics discussion in #2210. The issue is an overview tracker with its task breakdown still marked TBD, so completion criteria and a standalone starting task are not yet defined.