docs: update comment for startup versioning workaround

now that i know a *little* more about why it is needed

fix: move startup workaround for trainwreck query bug

apparently this workaround will break alembic commands since
versioning must be handled a bit differently in that scenario. so
must only do the workaround if versioning is enabled during the
startup sequence..

fix: add startup workaround for trainwreck query bug

not at all clear why, but c621e21cd4b4a2a408d8a32ace0b34afe6fdf526 has
introduced some strange bug where the "first" trainwreck query will
raise an error and yet subsequent queries work fine.

so now in the startup sequence we simply force a query, which for
unknown reasons does *not* raise any error, and will somehow magically
prevent the error when a "normal" trainwreck query happens later.

AFAIK this is a "benign" operation and causes no real side effects
other than preventing the strange error. fingers crossed, this is
fine and will not cause further problems...??!

fix: change import for wuttjamaican base model

must avoid importing the actual model subpkg from wuttjamaican because
it can interfere with sqlalchemy-continuum versioning

fix: move "record changes" global hook to startup()

this silly thing shouldn't even exist but can't remove until i'm
certain it's not in use in the wild.

but at least, it shouldn't be triggered when a config object is
instantiated, it needs to be deferred a little. should not affect app
runtime per se but more helpful for tests.

fix: cleanup old code for "record changes" session feature

had some tests failing, and one thing led to another.. apparenty we
still had support for some pretty old sqlalchemy so no need to keep
that around.

fix: hopefully fix startup continuum bug per 'active_history' models

only have one model in the wild (SpecialOrder) which uses
active_history and it probably shouldn't really.. it was written a
long time ago and would need some refactoring.

but for now we just need things to work, and this seems to do it
although i have no idea why

fix: avoid legacy config methods within `make_config()`

in case factory is WuttaConfig

fix: tweak how versioning is configured and confirmed

to allow for adding this to a wutta-native app

fix: use app.get_title() and app.get_node_title(); avoid deprecated calls

now that wuttjamaican app handler has both methods

fix: partially restore previous logic for `app.get_version()`

latest refactor for that was too aggressive, and tests complained

feat: refactor config/extension, session logic per wuttjamaican

this leverages wuttjamaican for a few more things perhaps, but mostly
this is to organize the code in a more logical way based on
conventions used in wuttjamaican.

fix: use `ModelBase` from wuttjamaican, as our model base class

this gives us better `dict(obj)` behavior

fix: grow column size for `MemberEquityPayment.amount`

to match CORE-POS `stockpurchases` table, otherwise it's possible to
fail importing that data

fix: stop logging config files read

upstream is already doing that

fix: add `rattail.util.render_duration()` function

so this can be called outside of app handler context, specifically
from a colander schema node

fix: stop setting falafel theme in installer

that is the same as current 'default' theme; and using falafel
requires an override of tailbone.themes.keys which we don't want to
bother doing

test: fix tests for `AppHandler.get_version()`

for some reason python-configuration is unreliable on certain python
versions? not sure what that's about, but this seems to work..

fix: `AppHandler.get_version()` should use upstream logic

but for now it needs a backward-compatibility wrapper

fix: invoke wuttjamaican logic for `rattail.util.prettify()`

eventually should deprecate that altogether since callers can now just
use app handler method

fix: rename auth handler; avoid app in provider constructor

if we reference `self.app` within the Provider constructor, then it
can (in some cases?) cause a recursion loop error

fix: avoid deprecated `self.model` for people handler

per wuttjamaican

fix: avoid deprecated `self.model` within the auth handler

per wuttjamaican

feat: move most of auth handler logic to wuttjamaican

also deprecate the `rattail.db.auth` module

fix: rename some constraints per wutta model

we will not (yet?) be able to "inherit" from the wutta model Base
which means basically the two are "not related" at this point.

but we do want to *match* whatever wutta has defined so far. the
rattail auth tables may contain more columns but will at least include
those columns present for the wutta model.

part of matching is the constraint names, which have been manually
specified in rattail for a while now. finally wutta has bothered to
define a proper naming convention so we can simply omit the names for
future changes. however it also means we must add an explicit
migration for any models we must match to wutta, to abandon the names
we had previously set which are now "incorrect"

most constraint names can remain as-is i think, since most tables will
never exist in the wutta model. eventually might be good to rename
all at once but that can wait

fix: remove duplicate method for `AppHandler.load_object()`

that is now defined in wuttjamaican

fix: remove duplicate method for `RattailConfig.production()`

since it now is defined in `WuttaConfig`

feat: move some app model logic to wuttjamaican

previously the "canonical" way to get the model was via
config.get_model() - but now the canonical way is simply app.model

note that for now, even though wuttjamaican provides a default model,
the rattail model does not (yet?) inherit from it. also since
wuttjamaican does not yet support versioning, that feature remains in
rattail only for now.

various legacy things have been deprecated and will warn if used by
other apps.

test: fix broken test

now that we are providing a default value for mail template paths. i
could not think of any reason we were *not* doing that before...?

fix: add `get_role()` method for auth handler

for common lookup logic; this is used when auto-creating users so
config can say which role to assign them to

fix: specify default list for rattail mail templates

not sure how this never came up before?

fix: add `get_cmd()` method for import handlers

now that we have no direct reference to command/subcommand objects,
must deduce them some other way for sake of locating correct email
profile config

fix: bump version for wuttjamaican

0.4.0 drops the legacy command system entirely, since we no longer use it

fix: avoid command line errors if sqlalchemy not installed

some commands will not work without sqlalchemy of course, but some
still need to (e.g. backup)

fix: refactor code so most things work without sqlalchemy

also refactor tests to help ensure that remains true

fix: bump wuttjamaican version requirement

to include changes for config, app handler etc.

fix: change how we override default app handler, engine maker

per upstream changes. this ensures we avoid the app handler when first
creating the engines, so that config extensions may override the
default app handler without being ignored.