Test double upgrades with locking views

[strk]

The bug reported in #5494 only affects running an upgrade procedure twice while a view holds back some deprecated function.

This resulted in no bots ever catching it, which is a pity. This ticket is to improve the testsuite to also test this case.

The double upgrade could re-use the existing pre-upgrade hooks to install the locking views, then run an ad-hoc test running an additional upgrade, and call all of this via run_test.pl —upgrade which would be doing the first upgrade.

I've done this locally but would like to automate it somehow.

I think running ALL tests would be overkill so this is really something we only want to do with an ad-hoc test

[Sandro Santilli <strk@…>]

In 84ed9355/git:

Have dronie and woodie test double-upgrades

References #5497 in master branch

[Sandro Santilli <strk@…>]

In a48a238/git:

Have woodie and dronie check locked upgrade for core

References #5497

[Sandro Santilli <strk@…>]

In 2cff249/git:

Have after-upgrade hook drop view created by use-all-functions.sql

Fixes make -C regress check-locked-upgrade

Also encode some skips due to known bugs

References #5497

[Sandro Santilli <strk@…>]

In 148267b/git:

Drop the upgrade test schema before the deprecated functions

Ensures the deprecated functions can be removed safely

References #5497

[Sandro Santilli <strk@…>]

In 27974085/git:

Drop any deprecated_by_postgis function after upgrade test

Fixes make -C regress/ check-locked-upgrade for real

References #5497

[Sandro Santilli <strk@…>]

In e9df666/git:

Skip all problematic raster functions from locking view

Have dronie/woodie run locked upgrade test also for raster

References #5497
References #5516

[strk]

At the moment "locked upgrade" is always tested by make check, due to regress/runtest.mk including the use_all_functions.sql hook. This means make check-double-upgrade is already testing locked-double-upgrade and both Dronie and Woodie are running make check-double-upgrade, so I'll close this ticket as completed.