There are recently added events that exist in the stage DB that have measurements with a uom and a null metric_id. This can occur when event messages or events from the API do not include both uom and metric_id.

This should be fixed so that we are not left with any bad data once UOM is removed.

The bad data can be identified as follows:

gabi "select org_id, min(record_date), count(*) from events where data->'measurements'->0->>'metric_id' is null group by org_id" 

DONE:

1. Update event ingestion via messages and API to make sure that both uom and metric_id are set before events are saved.
2. Update any existing events to have both metric_id and uom set to the same value as done here