Phoenix: Integration with FRESH for static sequence checking

[shaheerk94]

Checked for duplicates

No - I haven't checked

Alternatives considered

No - I haven't considered

Related problems

No response

Describe the feature request

Eric has gotten some funding from above to prototype a FRESH-Phoenix integration for static sequence checking. FRESH (Flight Rule Evaluation Sequencing Helper) is a tool that provides a means to check individual sequences for flight rule violations. See the user's guide here: https://github.jpl.nasa.gov/Europa-PESS/ec-fresh/blob/develop/docs/fresh_users_guide.md#overview. Also, see this area of the SEQ 2.0 architecture diagram for where it falls in the overall architecture diagram: https://www.figma.com/board/KAoIiLt3RTMY2008IocRkQ/Architecture-Diagrams?node-id=473-2216&t=ngcjBp0Du0H8YLQp-4. Lastly, see this user flow for static sequence checking: https://www.figma.com/board/ZkeSvi22sCPM3cB1Bj5mqD/User-Flows?node-id=511-3794&t=ngcjBp0Du0H8YLQp-4. We don't need to implement this whole flow for this prototype, though.

The overall idea is to implement an example of an external static sequence checker that can be called from phoenix. This roughly entails:

1. User configures FRESH static checking (points to CSVs, writes python checks)
2. User import or author a sequence in Phoenix
3. User clicks a button to run static checking on a sequence
4. UI sends sequence (SEQ JSON) to Python server that is running FRESH. Server performs checks on sequence and returns results
5. Results are made available to user (via linting?)