[Cell-level metadata] Make Process Project button show up for cell level metadata

[cosa65]

Background The behaviour is outlined here.

Make the "Process Project" button show up after uploading a new file. On click, instead of triggering gem2s, it triggers a qc rerun of the last step so that the metadata of the file gets inserted in cell sets. This doesn't require changes to the processingConfig because this info is stored in sql.

This ticket involves api and ui work and a migration.

Goal

• [x] In order to track which metadata file qc was last run with, we'll need to make use of the last_pipeline_params column in sql (for qc), it should begin to store which s3 file it was last run with in an object. Based on comparing this value and the one that references the experiment in cell_metadata_file_to_experiment.
• [ ] The cell_metadata_file referenced by the experiment should be returned from the api now as part of the experiment (just like we now add metadata and samples to the experiment before returning it to the UI).
• [ ] in the api's getPipelineStatus, for qc, shouldRerun should be returned set to true if the file ids in cell_metadata_file_to_experiment and last_pipeline_params don't match.
• [ ] Process project shows up (disabled) while upload is in progress.
• [ ] Process project shows up (disabled) if cell_metadata_file_to_experiment is in upload_status upload error.
• [ ] Process project shows up (enabled) if qc's shouldRerun is true and the file referenced in cell_metadata_file_to_experiment is in status uploaded.
• [ ] Send a flag to qc to run only cell level metadata and not clustering if the trigger was Process Project

[gerbeldo]

• Add a flag to run only cell level metadata and not clustering in the corresponding cases