PhET-iO instrumentation

[pixelzoom]

For #77.

Baseline version: https://phet-dev.colorado.edu/html/reactants-products-and-leftovers/1.3.0-dev.3/phet/reactants-products-and-leftovers_all_phet.html

---

TODO list

Convert from dynamic to static:

• ReactionBarNode: create all equations on startup
• RPALScreenView: create UI for all reactions on startup
• GameButtons: tryAgainButton, showAnswerButton, nextButton
• ChallengeNode: faceNode
• GameScreenView: settingsNode, playNode, resultsNode
• ResultsNode: rewardNode, levelCompletedNode
• PlayNode: currentChallengeNode
• GameModel: challenges
• StackNode

Misc sim-specific

• GameModel has an order dependency in several places (like this example), will this be a problem when restoring state?

    this.gamePhaseProperty.value = GamePhase.RESULTS; // do this last, so that other stuff is set up before observers are notified

Common Code:

• vegas FiniteStatusBar needs PhET-iO design, to determine what should be instrumented. (Do InfiniteStatusBar at the same time?)

[pixelzoom]

Publishing a PhET-iO version of this sim is no longer a goal for July 2023, see #77. But instrumentation is now in an awkward intermediate state, where pausing would leave the sim in a bad state. So I'll continue to chip away at this until it's in an acceptable place to pause.

[pixelzoom]

This is at a reasonable stopping point. The first 2 screens have a good start at instrumentation/reorganization. But since the Game screen reuses code from the first 2 screens, it's really impossible to continue further with the first 2 screens without addressing instrumentation of the Game screen. And before that happens, PhET-iO design for games (both general, and specific to this sim) needs to happen. Unassigning until it's feasible to continue.