Add `handlers` dict for app providers

they will each keep track of their own handlers, instead of adding to
main app..possibly should change that in the future, we'll see?

Add initial support for rattail "providers"

so integration projects etc. can supplement the main AppHandler
without subclassing it

Add `make_list_string()` method for config objects

opposite of `parse_list()`

Add `add_note()` method for custorder handler

and tweak item status/event enum labels to be more terse

Add global `--plus-config` command arg

can now omit `--config` to get "normal" config, and use
`--plus-config` to add some tweaks

Re-define custorder item status/event codes enum

pretty sure this is good enough to go live with...?

Add contact attempt fields for custorder item

also tweak some enums regarding those

Add `special_order` flag for CustomerOrderItem

also add `flagged` flag

and copy all product key fields when making order from batch

Must pass rows to `make_new_order()` for custorder batch

also allow passing `new_order_id` if `batch.id` is not wanted for order

Remove deprecated logic for legacy `Customer.people` schema

perhaps one day that will be used again, but for now remove the option
to avoid confusion

Add `product` relationship and `resolved` user/time for PendingProduct

when resolving, should keep a ref to new product record and who did it

Optionally configure SQLAlchemy Session with `future=True`

this avoids the need for setting `cascade_backrefs=False` everywhere

https://docs.sqlalchemy.org/en/14/errors.html#error-s9r1

https://docs.sqlalchemy.org/en/14/orm/session_api.html#sqlalchemy.orm.Session.params.future

Add `source` column for MemberEquityPayment

for cases where payments must be reconciled across systems

also wire up version importer for this model, whoops

Add `import_single_object()` method for ImportHandler

this may or may not be a good idea..? seemed pretty convenient for
use in a script though so we'll see

Add `get_label_profiles()` method for LabelHandler

just to make sure same logic is used in tailbone and byjove/api

Remove usage of deprecated `rattail.db.api` functions

now using handlers all around instead

Add generic base class for web API clients

tired of re-inventing this wheel, surely they can standardize somehow?
guess we'll see

Add setting for "max one member per person"

this should possibly be True by default? but for now we'll leave it
False by default, since that has "better" support thus far..

Version import should add "DELETE" record instead of deleting records

..right? we'll see if anything breaks

Set appropriate attr when assigning PO for receiving batch

if PO lives outside of Rattail, different attr must be used to track reference

Remove `autoincrement` kwargs for latest db migration

to avoid alembic warnings

Improve UOM choices for product info

better represent items sold by weight, for new/edit custorder

Preserve invoice number/date in credits for multi-invoice receiving

and make single-invoice work the same way

Add support for collecting 'python' telemetry data

just the envroot and python version so far..

Track invoice number for each row in receiving batch

in case of receiving from multiple invoices

Add `rattail auto-receive` cmd, as versioning workaround

when doing "auto-receive" for a receiving batch, need to disable
versioning as the process is too slow with it enabled

this also tweaks a couple of things that came up for KeHE

Rename module to `rattail.filemon.config_`

append underscore ('_') to avoid naming confusion for sake of running
filemon service on win32

there seems to be some issue with import paths in a win32 service
context. not sure why but it also bit me long ago with `rattail.csv`
module which is why that is named `rattail.csvutil` instead.

now the problem is within `rattail.config` we do `import config as
configuration` but somehow that gets confused and tries to import the
`rattail.filemon.config` module from within the win32 service. so
instead of getting to the bottom of that, we just rename with
underscore suffix to avoid the issue

Add `rattail filemon debug` command option for win32

to make troubleshooting a bit easier

Disable some tests, pending new mock

should fix someday..no time to do it today

Allow problem report emails to have attachments

for now each report must generate their own, if needed

Replace deprecated usage of `send_email()` function

use app handler instead

Fix how win32 service commands are ran, e.g. for install

must run command as e.g. `python -m rattail.filemon.win32` instead of
`python /path/to/rattail/filemon/win32.py` - latter will throw off the
import path / mechanism somehow and cause problems

Allow "arbitrary" PO attachment to purchase batch

for sake of other POS integration etc.

Add special bulk item handling for KeHE invoice parser

when "PackSize" column value is e.g. "1/11.000 LB" then must
re-calculate unit cost, case size etc. accordingly, instead of
assuming "1" is the case size

Do not trust unit cost from UNFI invoice

must calculate that instead, from "total" cost per item

Lower log level when enabling Continuum versioning

i guess we really should not see that normally..

Add basic autocomplete for Members

really just works on Person.display_name so far..

Remove fallback to customer when getting contact email

for some reason exceeded max recursion depth in production, though i
was not able to reproduce?! anyway this seemed to fix..

Add `--supported` arg for `rattail mysql-chars` flag

to show what the underlying DB engine supports

this also enables "live mode" which will actually attempt to modify
live DB / tables...fingers crossed

Add basic support for `quickie_lookup()` in people handler

meant to locate a person by e.g. customer number

Update usage of `get_product_key_field()`

avoid deprecation warnings

Add `get_short_display_name()` method for auth handler

supersedes `User.get_short_name()`

Revert "Add logic to allow/ignore cache objects which do not normalize"

This reverts commit f96f1794be463e955f3d833e033628a7aca978b9.

pretty sure that was misguided somehow..in particular the scenario
described in that commit comment is no longer quite relevant, as the
CORE -> Rattail import no longer uses that composite key

Prefer account holder, shoppers over legacy `Customers.people`

but until all are migrated, support both

also add `get_contact_email()` and `get_contact_email_address()`
methods to app handler; deprecate similar things in various places

Be a little smarter when parsing datetime values from CSV

sometimes they may contain microseconds