Branches 2.5 and 3.0 lost tests of upgrades in presence of data

[strk]

With commit [35b17931fdaa743c3f4f215ae9e8fc48f777dd02/git] in stable-2.5 and [a0c29068d31774ee9e85acc2c0ce685d7a4e3741/git] in stable-3.0 the run_test.pl script was updated to newest version thus loosing the hard-coded objects created before upgrade.

The new way to test upgrades in presence of data is using hooks but the use of hooks was not backported, leaving branches 2.5 and 3.0 uncovered from those tests.

In branch 3.1 I've backported those hooks with commit [6ec1e6cafcd53df5890fef65dc776ccd02313181/git] but 3.0 and 2.5 still need this threatment.

We badly need a "testsuite" component I think (buildbots seems more specific)

[strk]

WIP for 3.0 branch: ​https://gitlab.com/postgis/postgis/-/merge_requests/87

[robe]

Lets do this sometime after this next batch of releases.

[strk]

WIP for 3.0 branch migrated to gitea: ​https://git.osgeo.org/gitea/postgis/postgis/pulls/115

[Sandro Santilli <strk@…>]

In 7c2ecd1/git:

Re-enable upgrade-with-data tests

References #5214 for 3.0 branch

[strk]

WIP for 2.5 branch: ​https://git.osgeo.org/gitea/postgis/postgis/pulls/116

[Sandro Santilli <strk@…>]

In 6201c2f/git:

Re-enable upgrade-with-data tests

Closes #5214 in 2.5 branch