Upgrading extension from 3.2.1dev puts tiger twice in session search_path

[strk]

xxx=# create extension postgis_topology version '3.2.1dev' cascade;
NOTICE:  installing required extension "postgis"
CREATE EXTENSION
xxx=# create extension postgis_tiger_geocoder version '3.2.1dev' cascade;
NOTICE:  installing required extension "fuzzystrmatch"
CREATE EXTENSION
xxx=# show search_path; -- known issue
      search_path
------------------------
 "$user", public, tiger
(1 row)
xxx=# \c
You are now connected to database "xxx" as user "strk".
xxx=# show search_path; -- known issue
      search_path
------------------------
 "$user", public, tiger
(1 row)
xxx=# select postgis_extensions_upgrade();
NOTICE:  Updating extension postgis 3.3.0dev
NOTICE:  Updating extension postgis_topology 3.2.1dev
NOTICE:  Updating extension postgis_tiger_geocoder 3.2.1dev
                              postgis_extensions_upgrade
---------------------------------------------------------------------------------------
 Upgrade to version 3.3.0dev completed, run SELECT postgis_full_version(); for details
(1 row)
xxx=# show search_path; -- THIS issue
      search_path
------------------------
 tiger, "$user", public, tiger
(1 row)
xxx=# \c
You are now connected to database "xxx" as user "strk".
xxx=# show search_path; -- we're OK after reconnect
           search_path
----------------------------------
 "$user", public, tiger, topology
(1 row)

[strk]

It looks like it is the tiger.SetSearchPathForInstall function adding the tiger prefix in search_path, meant to be for install. I guess @extschema@ should be used instead

[robe]

I think this might be resolved, but will need to check later. I'll keep open for now.

[robe]

I'm pretty sure we resolved this but don't have time to test.