Arrange to get Agoric NPM packages fixed and absorb the results #337
Description
The changes introduced by PR #317 include importation of a couple of Agoric NPM packages that have proven to be malformed for purposes of incorporation into a TypeScript project. Agoric is aware of the problem and is sympathetic, but as of now it's unclear who, if anybody, is best positioned to fix this. As is, PR #317 includes a number of ugly workarounds to deal with the current state of things, and these are brittle in the face of likely further evolution of the Agoric packages under maintenance. We need to either do what it takes to get Agoric to fix the NPM packaging or figure out a fix ourselves and send them a PR (which, if we do, they've assured us they'll happily accept). Once the better packaged packages are pushed to NPM, we then need to unwind the aforementioned workarounds.