Peg `invoke` version to pre-2.1

apparently 2.1.1 has same problem as 2.1.0

hopefully can remove this in a few weeks; cf.
https://github.com/fabric/fabric/issues/2263#issuecomment-1532107759

Add version restriction for `invoke` lib

per bug in latest release

Remove version cap for plaster lib

no longer relevant here

Remove dependency for pyramid_retry

since tailbone now includes it

Add support for new-style `rattail-demo install` command

also use upstream menus where possible

Refactor various views and config, per upstream changes

adding proper integration support for CORE, WooCommerce

Remove version cap for mysql-connector-python

live demo now runs on python 3.9.2 and so whatever issue i ran across
previously, is no longer a thing i guess.

might as well not declare any particular python version beyond "3" ...

also cleanup the rattail dependencies a bit

Update some view config

per upstream changes

Purge things for legacy (jquery) mobile app

per upstream purge

Override the CORE-API -> Rattail Demo importer for Store data

this lets the demo have random extra Store records and the importer will just
ignore them

Expose the Units of Measure views in web app

also this declares the CORE-specific product handler to be our default

Remove custom logic for preventing password change for 'chuck'

upstream now handles this

Add initial Shopfoo pattern feature

data models, import/export, web views etc.

Cap version for mysql-connector

dang it, what is up with that thing? oh well, can look into it later..

Be smarter about how we prevent edit/delete for some people, employees

instead of just hard-coding UUID for 'chuck'

Stop protecting certain settings from being edited

we no longer expose settings to 'chuck' user etc.

Tweak how we show pyCOREPOS package version

per upstream changes

Fix inventory batch views

per upstream changes

Add Tempmon Appliance views, menu link

also remove edit/delete restrictions for tempmon clients, probes. now we just
let the normal permissions handle that

Remove custom logic for User views

this was to protect the 'chuck' user but we now have better (upstream) ways

Remove time clock, schedule views

those weren't very well supported, and that won't change anytime soon

Tweak project name for tailbone-corepos

i.e. for About page

Move jump button logic to tailbone-corepos

since that now supports jump button for Vendor also, maybe others to come

Define custom data model; add alembic scripts; etc.

actually our "custom" data model is just rattail + rattail-corepos

Fix basic product editing feature

limit which fields are supported

Fix home, login templates for Buefy

per recent upstream changes

Remove CORE-POS web views logic

all the views are still visible in our app, but the view logic belongs in
tailbone-corepos now

Add rattail dependency, for sake of eager upgrades

to bring in sqlalchemy-continuum upgrades etc.

Remove deprecated menu template

using "simple" menus exclusively now

Delete 'bobcat' theme override

core bobcat theme now supports simple menus natively

Refactor web app to use "simple" menus

for sake of sharing between themes

Tweak style for header logo

seemed necessary for sake of bobcat theme, but worked for default too..

Fix template references for app_title

make sure we only look to /base_meta.mako for that

Move base template to /base_meta.mako

per upstream 'themes' feature

Add feature demo for importing Square transactions to CORE-POS

also allow delete of CORE-POS transactions, for sake of demo

Add version caps for pyramid etc.

so that we don't have to cap things within tailbone

Change how we prevent edit/delete for demo users

to take new 'demo' user into account, but also more readable