Remove `bash -c` prefix for `pg_dump` command

need to keep the `sudo -u postgres pg_dump ..` part as simple as
possible, since must declare `sudoers` allowance for that

Add option to skip raw SQL file when dumping postgres DB

trying to cut down on disk space, we'll see how well this works..

Try again, to move postgres dump file to /tmp before restoring

so the postgres can cd to current workdir without error..fingers
crossed this doesn't break anything else again

Revert "Move sql file to temp path when restoring postgres db"

This reverts commit 94945fbc306575f3a855e40db61ec916e1e2e073.

apparently that breaks some nightly cloning (prod -> stage)

Add `clang` workaround for pythonz

needed that to install python 3.6.8 on debian 12

Move sql file to temp path when restoring postgres db

otherwise postgres may throw an error, if it can't cd to current workdir

Let caller override default `fannie/config.php`

also make `deploy.full_path()` honor absolute path when given one

Do not define rattail mail templates by default

pretty sure that value was/is already fallback default anyway

Add a couple more options for `rsync()`

sometimes you just need something different to happen..

Add `__version__` attr to root namespace

for sake of `setup.cfg`

Touch `debug_fannie.log` when installing CORE

just to prevent the warning

Use `--global` when allowing Composer plugins for CORE

this keeps allowances out of the local `composer.json` file and
therefore keeps the working folder clean

Add new/improved `install_corepos()` function

probably needs still more improvement, but getting here. so far it
only does the office setup

Add `make_normal_user()` function

also add `disabled_password` kwarg for `make_system_user()`

Remove some luigi config if using newer package

apparently some of these settings are no longer used by latest luigi,
and it complains when they're present

Fix logic to bind postgres to all network interfaces

ugh, finally solved this

Inject default mail sender/recips for machine-wide `rattail.conf`

also tweak timezone handling

Don't write overnight scripts to invoke luigi directly, by default

`rattail overnight` command can handle that natively now

Make each overnight script optional

trying to phase out at least 1, maybe 2 of them...

this also cleans up the 'restart' script to use 'rattail overnight'
per recent changes. this seems the most useful to have around, in
case of web app failure

Use new `rattail overnight` command in `cron-overnight.sh` script

this is all a bit of WIP at the moment, perhaps..

Use `shlex.join()` when adding postfix alias

a bit convoluted perhaps, but still better...

Tweak logic for setting PostgreSQL `listen_addresses`

this still isn't right, but i'm calling this a savepoint at least

Tweak default luigi config; allow specifying version

to accommodate one particular install, but is generally okay i think..

Add `--progress-bar` arg for pip in backup app's upgrade script

for some reason latest pip has progress bar showing up in cron output
and causing unwanted email

Add generic Luigi install logic

at least try to do what we can to reduce boilerplate

Use python instead of shell script, for datasync checks

seems to give more clarity, and we'll have more options this way

Add `bootstrap_rattail_base()` and related tweaks

the idea here is to have a "one stop shop" for base requirements,
we'll see how useful it is in practice i guess

Avoid use of `workon` when deploying backup app

should not assume presence of virtualenvwrapper for this

Allow skipping of triggers when dumping MySQL DB

specifically this is b/c of a production demo which makes use of multiple
triggers of the same "type" but my dev maching has older MariaDB which doesn't
allow such multiple triggers

Tweak how python packages are installed for backup app

per some issues i encountered with pip 20.3.3 and its "new resolver" although
not totally clear what fixed it... :/

Add `python.configure_pythonz()` convenience function

not sure how i managed to get by without this until now..?

Add basic `ejabberd` module

doesn't do much really, but still worth sharing i suppose

Don't use sudo for parts of `postgresql.restore_db()`

since apparently that is a problem

Add `port` and `user` kwargs for `ssh.cache_host_key()`

deprecate the `for_user` kwarg. this also will now try a basic command over
ssh before bothering with an update/cache for the host key

Split up the dump/restore DB logic for postgresql

so that i can swap out portions of that in order to use rsync for big DBs

Try to set mysql user password in 2 different ways

so some versions of MySQL and/or MariaDB do not agree as to how the password
should be set? weird, but oh well, hopefully this works everywhere...

Allow specifying python binary for common backup app environment

also be sure to upgrade setuptools, wheel for it. this is needed esp. when
deploying to older machines e.g. debian 8

Change how we set password when creating a MySQL user

the way we were doing it just failed on MySQL (proper, not MariaDB) 8.0

Add `method` kwarg for `python.install_pip()`

ugh, this still needs to be better probably

Require the 'rattail' package

just for convenience, might as well