🐛 Clinical-Errors endpoint returning multiple records for single donor, some with no errors

[joneubank]

Describe the bug

The api response to the data endpoint clinical-errors can sometimes return multiple objects for the same donor, and in unknown cases the list of errors is returned as empty.

The shape of this response would look like:

{
  "clinicalErrors": [
    {
      "donorId": 1234,
      "submitterDonorId": "ASDF_1234",
      "entityName": "primary_diagnosis",
      "errors": []
    },
    {
      "donorId": 1234,
      "submitterDonorId": "ASDF_1234",
      "entityName": "treatment",
      "errors": [
        {
          "donorId": 1234,
          "entityName": "treatment",
          "errorType": "INVALID_ENUM_VALUE",
          "fieldName": "treatment_setting",
          "index": 0,
          "info": {},
          "message": "The value is not permissible for this field."
        }
    ]
}

Steps To Reproduce

Unclear. Visible in production PACA-CA data.

Expected behaviour

Message response would have a single object for any given donor, and never include a donor with an empty errors list.

{
  "clinicalErrors": [
    {
      "donorId": 1234,
      "submitterDonorId": "ASDF_1234",
      "entityName": "treatment",
      "errors": [
        {
          "donorId": 1234,
          "entityName": "treatment",
          "errorType": "INVALID_ENUM_VALUE",
          "fieldName": "treatment_setting",
          "index": 0,
          "info": {},
          "message": "The value is not permissible for this field."
        }
    ]
}