refactor(robot-server,api): wire up JSON protocol runner to /sessions

[mcous]

Overview

This PR gets us pretty close to #7808.

• You can create a protocol session from an uploaded JSON protocol file
• On session creation, a JSON protocol runner is created and loads the protocol state into a Protocol Engine
• You can issue a start action to kick off the run

There's still a few items to address before I think 7808 can be considered complete, but we're almost there!

• Pipette and labware loading into the Engine from the JSON protocol data (I think?)
• Get next command from the queue (feat(protocol-engine): Implement CommandState.get_next_request() #7936)
• Translation of all JSON protocol commands that we could support in the CommandTranslator

Changelog

• Implement a basic version of ProtocolEngine::add_command
• Create ProtocolSession response model type(s)
• Allow the EngineStore to create and load an AbtractFileRunner if needed

Review requests

• I have no idea what will happen if this gets run on a robot
• This is pretty hard to smoke test without HTTP protocol: command status of engine-backed protocol session #7871
• Do the changes / TODOs all make sense?

Postman testing collections here

1. POST /protocols with a JSON protocol
   • I took the protocol at shared-data/protocol/fixtures/5/simpleV5.json and stripped out all the commands that CommandTranslator doesn't know about
2. POST /sessions with sessionType: "protocol" and createParams: { protocolId: "{{ protocol_id }}" }
3. POST /sessions/{{ session_id }}/actions with actionType: "start"

Risk assessment

Low. Feature-flagged endpoints.

[codecov]

Codecov Report

Merging #7935 (7d58098) into edge (875e86a) will decrease coverage by 9.62%.
The diff coverage is 95.91%.

@@            Coverage Diff             @@
##             edge    #7935      +/-   ##
==========================================
- Coverage   93.48%   83.86%   -9.63%     
==========================================
  Files         130      352     +222     
  Lines        5141    21730   +16589     
==========================================
+ Hits         4806    18223   +13417     
- Misses        335     3507    +3172     

Impacted Files	Coverage Δ
robot-server/robot_server/sessions/session_view.py	95.65% <66.66%> (+0.41%)	⬆️
robot-server/robot_server/sessions/engine_store.py	97.36% <93.33%> (-2.64%)	⬇️
robot-server/robot_server/protocols/__init__.py	100.00% <100.00%> (ø)
...obot-server/robot_server/sessions/action_models.py	100.00% <100.00%> (ø)
robot-server/robot_server/sessions/router.py	100.00% <100.00%> (+3.27%)	⬆️
...bot-server/robot_server/sessions/session_models.py	100.00% <100.00%> (ø)
opentrons/commands/protocol_commands.py	94.73% <0.00%> (ø)
opentrons/api/util.py	92.59% <0.00%> (ø)
opentrons/protocol_api_experimental/labware.py	81.53% <0.00%> (ø)
opentrons/hardware_control/simulator_setup.py	97.91% <0.00%> (ø)
... and 218 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 875e86a...7d58098. Read the comment docs.

[mcous]

This may raise a ProtocolNotFound (or something) error from the ProtocolStore and needs to map to a 404

[SyntaxColoring]

Paired and reviewed in a call. Looks good to me, assuming CI passes. 🦜 🕺