feat(robot-server,app): add download deck calibration button

[ahiuchingau]

closes #6055

Overview

This PR adds a download deck calibration button per this design.

Changelog

Robot server:

• add DeckCalibrationData model with fields: type, matrix, lastModified, pipetteCalibratedWith, tiprack
• update get calibration status endpoint based on the deck calibration type
  • old deck calibration data found in /data/ will only contain the type MatrixType.affine and the matrix data
  • new deck calibration data in /data/robot/ will have the type MatrixType.attitude, matrix data, information on the pipette and tiprack used in calibration

App:

• new DeckCalibrationDownload component that renders whenever the deck calibration status is not null
  • renders last modified date time only if the deck calibration type is attitude (affine deck cal doesn't contain info on when it was last modified)

Component:

• add a download icon

Review requests

Put this on your robot, you should be able to download your deck calibration file in robot settings on the app:

1. enable the calibration overhaul feature flag on your robot
2. complete new deck calibration if you haven't already
3. you should be able to see when the deck calibration was last calibrated as follows
   
4. download calibration file, the default file name should be {your-robot-name}-deck-calibration.json
5. the downloaded file's format should look like:

{
  type: 'attitude',
  matrix: [[]],
  lastModified: 'somedatetime',
  pipetteLastCalibratedWith: 'pipetteID',
  tiprack: 'tiprack hash'
}

6. make sure the info is the same as the data/robot/deck_calibration.json
7. switch off the calibration overhaul feature flag
8. see that the last modified field disappears
9. download calibration
10. the downloaded format contain the same info as the old deck calibration data in data/deck_calibration.json

{
  type: 'affine',
  matrix: [[]]
}

Risk assessment

Medium since this PR modifies an existing endpoint and alters the look of the robot settings tab on the app.

[sfoster1]

Looks good in general but there's some little stuff to change.

[sfoster1]

This could I think be done with tuples to properly set the length of each row and the number of columns (at least, I think - I assume that pydantic properly translates that into a json array with a fixed number of elements)

[sfoster1]

If we're going to keep the app compatible with the last version of the robot as well as the current one, we should probably handle it here. I think the general use of null coalescence makes it work, but maybe add a test based on the robot returning the old style of the affine matrix directly in data?

[sfoster1]

We should get the loaded version from the hardware controller if possible. I'd like to start avoiding reloading stuff from disk every time.

[sfoster1]

probably needs one fewer !anyfloat

[ahiuchingau]

I thought it should be 4 in this case because an affine matrix would still have 4 columns

[sfoster1]

Yeah I think you're right

[sfoster1]

Code LGTM once you fix the type checks