Consider restructuring as a Lerna monorepo

The DynamoDB tooling you guys have written is very useful, but it's spread out over half a dozen packages, and in my experience projects like that can be hard to keep in sync. The monorepo style has been used a lot recently, and it may be a great fit here. You still maintain package-level modularity for the individual tools, but you can pull development tasks (linting, testing), to the top level project, test everything as a complete system, and automate `npm-linking` of inter-package dependencies.

Start by inventorying the half-dozen packages and their current linting, testing, and inter-package linking workflows. Done would require a defined Lerna monorepo structure that preserves package-level modularity and supports top-level development tasks, complete-system testing, and automated npm-linking.

Written by the indexing model from the issue text.