Fix that db dumps cannot currently be restored as-is

[Venryx]

Issue 1) Due to dependency ordering

Specifically: The problem stems from the cached-tsvector columns referencing utility functions, which pg-dump is placing after the table-creation lines in the sql dump.

Another solution to this may be to simply get rid of those auto-generated columns, and use the (slightly modified) indexes for that purpose.

Issue 2) Due to search-path config not getting exported as part of dump

[Venryx]

As of 2023-04-03, the dependency-ordering issue did not seem to be a problem; I did a restore from a logical backup just fine without messing with cached-tsvector columns <> table-creation conflicts or the like. (see pg-dump module in readme, in restore section, for some quirks that are still needed; not really a problem as is, though)