As the app stages are more independent in the Solara version of the app than they were in the voila version, it makes more sense to store stage states separately from one another. This PR adds the basic infrastructure for getting and creating/updating stage states. The unique key for the stage states table is (student ID, story name, stage name). I've decided to go with a stage "name" rather than using the stage index - while the stage indices for the Hubble story are pretty well set at this point, future stories will obviously be more fluid as they get developed, so it will make things easier if we don't use the ordering as our key here.
As the app stages are more independent in the Solara version of the app than they were in the voila version, it makes more sense to store stage states separately from one another. This PR adds the basic infrastructure for getting and creating/updating stage states. The unique key for the stage states table is (student ID, story name, stage name). I've decided to go with a stage "name" rather than using the stage index - while the stage indices for the Hubble story are pretty well set at this point, future stories will obviously be more fluid as they get developed, so it will make things easier if we don't use the ordering as our key here.