Ensure we have a workable every-day-use Poetry managed code base, to which we can address maintenance fixes (in master) while leaving our testing channel for our larger progressively urgent Python update.

In our current testing channel we have migrated our dependency & build system from the now legacy Buildout to the new shiny of Poetry. This should enable our greater goal of updating our Python base. But we must first ensure that our Stable (master branch) is similarly built: which is the purpose of this milestone.

All issues/pull-requests here are intended to establish our first stable release built using Poetry.