feat(app, api-client, react-api-client): send CSV RTP file to robot before creating protocol and run

[ncdiehl11]

Overview

The new RTP paradigm for utilizing CSV files as runtime parameters requires sending the ID of the file to be used as the value in the runTimeParameterValues object sent with createProtocol and createRun. Here, we send any selected RTP files to the new /dataFiles endpoint and await the response containing an ID for each file. We then associate the returned ID with its respective runtime parameter variable name, and send that key:value pair along with the other value runtime parameters.

Test Plan

This is a little tricky to test right now because the /dataFiles endpoint is not yet wired up, and the /protocols and /runs endpoint only accepts <variableName>: <value> pairs for runTimeParameterValues, not the new format of <variableName>: {file_id: <id>} for CSV parameters.

Protocol card and detail

• upload protocol that requires CSV file parameter like this:
  rtp_tests.py.zip

• verify that CSV file required banner renders on protocol card

• select protocol card

• verify that CSV file required banner renders on protocol details

Changelog

• post CSV files from RTPs when confirming values on both ChooseProtocolSlideout and ChooseRobotToRunProtocolSlideout, and use returned IDs in runTimeParametersValues sent with createRunFromProtocolSource
• fix MiniCard warning text margins on above slideouts
• update getAnalysisStatus util to return new parameterRequired status when analysis result is parameter-value-required
• refactor useCreateProtocolMutation to accept runTimeParameterValues argument in its returned mutation's callback rather than in the hook's invocation itself
• update tests

Review requests

Go through flow of uploading a CSV parameter protocol according to test plan above. Expected behavior is for a runCreationError to be raised when confirming value because the robot server does not yet know what to do with CSV parameter runTimeParameterValues overrides.

Risk assessment

medium

[koji]

@ncdiehl11

The design doesn't have info icon next to CSV file. Maybe we don't need to display that for CSV file?

[ncdiehl11]

@ncdiehl11

The design doesn't have info icon next to CSV file. Maybe we don't need to display that for CSV file?

@koji Do you mean for the description?

I mean literary the icon.
Your branch displays icon next to CSV Data. But in the design there is no icon (the above screenshot).
I'm not 100% sure that removing the icon is intentional or not.

Another is Name of csv file.
The design says CSV File which I'm also not 100% sure this is the fixed text or displayName since csv file row is the unique can be the fixed text or displayName.
Probably we would need to ask about this to Rob/Mel.

[koji]

left a comment about Parameter Table's csv file part, but the changes look good to me.