Ispyb

-------------------

* Modify stored procedure ``upsert_session_for_proposal_code_number`` to remove
references in queries to previously removed ``BLSession`` columns.

-------------------

* Add stored procedure ``retrieve_grid_info_for_dc_v2`` similar to
``retrieve_grid_info_for_dc``, but with micronsPerPixelX,Y columns instead of
pixelsPerMicronX,Y.

* Removed columns in ``BLSession``: projectCode, sessionTitle,
structureDeterminations, dewarTransport, databackupFrance, databackupEurope,
expSessionPk, operatorSiteNumber, protectedData

* Remove columns in ``DataCollectionGroup``: ``workflowId``

* Remove tables: Pod, PHPSession, Log4Stat, Particle, EMMicroscope, DataReductionStatus,
SAFETYREQUEST, SAMPLECELL, SAMPLEEXPOSUREUNIT, SAXSDATACOLLECTIONGROUP,
WorkflowStep, WorkflowType, WorkflowMesh, Workflow, AssemblyRegion,
AssemblyHasMacromolecule, Assembly, Structure, SubtractionToAbInitioModel,
MeasurementToDataCollection, Instruction, Merge, Measurement, AbInitioModel,
ModelToList, Model, ModelList, FrameSet, Run, FrameToList, Frame, FrameList,
BufferHasAdditive, MeasurementUnit, MacromoleculeRegion, Subtraction,
Stoichiometry, Additive, Specimen, StockSolution, Buffer, Macromolecule,
SafetyLevel, SamplePlatePosition, SamplePlate, PlateGroup, InstructionSet,
PlateType, SaxsDataCollection, Experiment.

-------------------

* Tables:

* Drop: ``MotionCorrectionDrift`` and remove it from schema files
* Add: ``BFactorFit`` with foreign key referencing ``ParticleClassification``

* Columns and keys:

* Make ``Dewar.shippingId`` not nullable
* Add: bFactorFit-related columns in ``ParticleClassification``
* Add: self-referenting foreign key column ``parentContainerId`` in ``Container`` to allow hierarchy of ``Container``s
* Add: ``containerTypeId`` foreign key column for the ``Screen`` table
* Add: ``manufacturerSerialNumber`` in ``DewarRegistry`` table
* Add: ``EORINumber`` column in ``Laboratory`` table to help with international shipping
* Add: ``riskRating`` enum column to the ``BLSession`` table to hold the ERA status
* Add: ``globalAlignmentQuality`` in ``Tomogram``
* Add unique key for ``ContainerRegistry.barcode`` and make it not nullable
* Extend ``BLSession.beamLineOperator`` to 255 characters

* Stored procedures:

* Drop: ``upsert_motion_correction_drift``, remove procedure file and remove it from the schema files
* Add: ``upsert_adminvar`` to upsert rows in the ``AdminVar`` table
* Add: ``update_reg_container_barcode``
* Add: ``update_session_enddate``

* Misc:

* Add: maintenance script to delete a given number of rows from a table, and then rebuild the table to reclaim the space for the OS
* Add: maintenance script to update BLSample.subLocation via a cursor in order to remove rows with duplications of (containerId, location, subLocation)
* Add: ``SELECT`` grants on ``ProcessingJob``, ``ProcessingJobImageSweep`` tables for role ``ispyb_scripts_processing``

-------------------

* New stored procedure ``upsert_dc_grid_v2`` and ``EXECUTE`` permission on it for the relevant role

This automatically creates a release commit and a release tag.
You then need to push both to the Github repository:
bash
git push pushes the release commit
git push origin v2.0.0 pushes the release tag for version 2.0.0


Assuming the tests pass the release is then created by Azure and uploaded directly onto [pypi](https://pypi.org/project/ispyb/).

The ISPyB API is also released on [conda-forge](https://github.com/conda-forge/ispyb-feedstock), the release process there will be triggered automatically within a few hours.

-------------------

Bug fix: The file name of an update .sql file didn't correspond with the name it inserted into the ``SchemaStatus`` table.