In ui/analyse/src/ctrl.ts, have this.data.game.status be updated on each move/jump

[johndoknjas]

I added the following debugging code in a branch of mine (the only relevant line is 596, and the issue isn't specific to premove scenarios):

I also made a study chapter that initially was not in a drawn state:

Then once playing a move to reach a stalemate, and doing a premove to trigger my console.log statement:

The status is incorrectly still 'created', when it should be 'stalemate' or at least 'draw'.

Note that if the initial position of the chapter were drawn, the status is correct. E.g. (ignore the other unhinged debugging statements):

If this is fixed, it would allow #16679 to rely on computations from the backend rather than the frontend, and make the logic cleaner. I've tried to fix it myself but haven't been successful.

[schlawg]

Note - this PR and #16679 both touch on areas of client analysis code that are likely to be disconnected from lila-ws and rewritten to use chessops within a month or two.