Sequence IDs not persistent in a plan

winner
https://jira.jpl.nasa.gov/browse/AERIEQS-274
High
Sequence IDs appear to be attached to the simulated data set of a plan, not the plan itself. This is a major user issue because it means if anything in the plan changes and it needs to be re-simulated in order to make the expansions, every sequence needs to be recreated from scratch by first defining the sequence and then attaching every activity which should be in that sequence to the sequence again. This is not only a very tedious manual process, but in plans that have any significant number of activities, it is a huge risk of user error when re-assigning sequences to activities because there is no way to automate this process.

The expected behavior is that defined sequences would persist within a plan, and activities would stay attached to a sequence ID when the plan is resimulated unless that sequence ID has been deleted.

This is related to AERIEQS-272 Can't add SEQ ID to activity before simulation and AERIEQS-273 SEQ IDs are not inherited from parent activity.

Start by tracing how plans, simulated data sets, sequence IDs, and activity assignments are represented and recreated during resimulation. Review related issues AERIEQS-272 and AERIEQS-273 for surrounding behavior. Done means sequences persist with the plan and activities retain their sequence IDs across resimulation unless the sequence was deleted.