point DB updates missed during 2.0-2.1.0 upgrade

Today we countered a database that had been upgraded from 2.0.5 directly to 2.2.0. However, it appears that the equivalent of the 2.0.8-2.0.9 update was missed, meaning that in particular revision 0601 for bug 825303 didn't make it into the database.

12 years later, the best hold sort selection sort order fails with the following error:

  ERROR: more than one row returned by a subquery used as an expression [for Statement "
        SELECT
            cbho.pprox, cbho.hprox, cbho.owning_lib_to_home_lib_prox, cbho.aprox,
            cbho.approx, cbho.priority, cbho.cut, cbho.depth, cbho.htime,
            cbho.shtime, cbho.rtime
        FROM config.best_hold_order cbho
        WHERE id = (
            SELECT oils_json_to_text(value)::INT
            FROM actor.org_unit_ancestor_setting('circ.hold_capture_order', ?)
        )
        "]

A patch to ensure that the revisions that were potentially miss-able when running 2.0-2.1-upgrade-db.sql as is could avoid this problem in other (very old) Evergreen databases. Alternatively, a more ambitious schema comparison script could help.