taskw

Bugwarrior currently depends on [taskw](https://github.com/ralphbean/taskw/) to interface with the taskwarrior database. While there is an implementation which interacts with the taskwarrior-2 database files directly, bugwarrior has for some time used the interface which interacts through the `task` shell command. This turned out to be a fortunate choice, because bugwarrior continues to work with taskwarrior-3 even though it has a totally different database.

However, taskw currently lacks much in the way of maintenance. Ralph offered to transfer taskw to GothenburgBitFactory earlier this year, but there were some communication issues which prevented that from happening. I don't think there's any question that this is an option and that all parties are open to it, but I am unsure who has the interest and skill to maintain taskw if that transfer were made. I would be willing to try to help if that were the path forward, but my recollection is that taskw maintenance was particularly difficult because it was hard to fix something for one dependent application without introducing bugs in another dependent application.

I'd be remiss if I didn't mention that I've become aware of [taskw-ng](https://github.com/bergercookie/taskw-ng), a fork (or rewrite?) which appears to be maintained. It also might be worth considering asking bergercookie to be a taskw maintainer if it were to be transferred to GothenbergBitFactory. I haven't looked at it closely at all.

In addition to the current lack of a maintainer, we have always had a few buggy edge cases in which certain data can't be serialized such that it is interpreted correctly by the shell. I suspect we're dealing with another one in #1075, which got me thinking about this this week.

Another option at this particular moment would be to create a taskw shim package in bugwarrior which mimics the small portion of the taskw API we currently use and integrates with taskchampion (the taskwarrior-3 database). We could then use our shim package and fall back to the real taskw for taskwarrior-2 users. (The motivation to continue supporting taskwarrior-2 may expire before this issue is resolved, in which case the shim API is irrelevant...) I created a separate issue about integrating with taskchampion: #1077