Mark all releases as `released after revalidation`

[peterdesmet]

See #236 (comment)

Detect observations that meet the following criteria:

1. The capture (1st record) is done by a user_name that contains VOC
2. The release (2nd record) is done by a user_name that contains VOC
3. The release (2nd record) does not have observation_condition == "released after revalidation"

All those records should get an observation_condition == "released after revalidation" in the source database.

[peterdesmet]

1,591 birds meet the first 2 requirements (i.e. first 2 records are from VOC). Of those, 165 don't have observation_condition == released after validation

[peterdesmet]

@EricStienen here's a CSV with all 165 observations that should be marked with released after revalidation. They are all the 2nd observation in a life history, have a VOC observer and follow a (1st) observation with also a VOC observer. According to #236 (comment) those should be considered releases and it's best to indicate this as such in observation_condition:

2nd_voc.csv

[EricStienen]

All, except those were the bird was found dead. In the image below, a typical sequence (B-CTOP), where the brid was

1. first ringed by the VOC in the rehab centre (28/07/2017 => should be noted as capture & healthy and alive)
   2 next released by the VOC at the beach of Raversijde a few days later (30/07/2017, should be observation (or eventuelly capture) & realsed after rehabiliation)
2. and in this case brought back to the rehab centre as a dead bird/or bird was euthanised immedatiatly after intake (obserrvation & dead)