Always log $$ in dequeued messages

The pid is rarely needed, but when it's needed it's really needed. And
with the auto-restart behaviour, it really comes in handy.
Use & instead of ; to separate parameters

Mojolicious #2d1cf0 removed support for ; because the "HTML Living
Standard" says that the serialization of form parameters must use &
as a separator. I always liked ; more than &, but it's not actually
worth doing anything about.
Accept both X-F-Proto "https" and X-F-HTTPS "1"

(Mojolicious 4.97 deprecated the latter, and 5.0 removed support.)
Replace render(partial=>1, …) with render_to_string()
No need for Gadwall::Log, thanks to format callbacks
We depend on the frontend server to preserve Host:
Replace Makefile.PL with cpanfile

The Makefile.PL existed only to allow "cpanm --installdeps .", but a
cpanfile works with both cpanm and carton.

(Note that we won't run carton here. It's up to projects that use
Gadwall to run carton and produce their own bundles. This cpanfile
is just a start.)
Add a top-level "use 5.14.0"

Now that Debian ships 5.14.2, I can't imagine wanting to install any
Gadwall applications on older versions of Perl.
Bundled libraries will be in local/lib/perl5

Instead of installing dependencies by hand into deps (with
"perl Makefile.PL PREFIX=~/deps LIB=~/deps/lib"), we'll use
carton, which puts things into local/lib/perl5.
Declare testing dependencies too
Add an './app exec …' command
Introduce db_owner{,_pass} config variables

We want to move away from schema/defs being the only place that knows
about our two-database-users scheme, so that we can avoid hardcoding
the owner's name in utility scripts and the like.
Introduce a 'schema install' command

This is a straight port of utils/setup-schema. It doesn't try to do
anything clever yet (such as not creating the users or database if
they already exist).
Another reversal of db_name/db_user
Introduce a 'schema upgrade' command

Again, this is a straight port of utils/upgrade-schema, with no attempt
to be clever.
Accept '--psql /path/to/psql' and revise usage accordingly
Allow 'schema install' to be run as user postgres
Get rid of {setup,upgrade}-schema and schema/defs
PL/PgSQL has been enabled by default for a long time
Accept '--schema $s' and create objects within that schema

Everything goes into that one schema, there's no support for putting
different components into different schemas.