chore: add adio and clean up transitive dependencies

[TillaTheHun0]

Due to the way yarn workspaces hoists dependencies and in combination with node's module resolution strategy, it is easy to consume a dependency not specified in my own package.json if that dependency is declared by another package and then hoisted by yarn.

For example, package A and B could specify crocks as a dependency in their package.jsons. yarn will appropriately hoist this shared dependency to the root node_modules. However, this means package C can now require('crocks') without specifying crocks as a dependency in it's own package.json file. This is otherwise known as a "transitive dependency". This isn't exclusively an issue in a monorepo, it is just exacerbated by a monorepo and hoisting strategy like that used by yarn workspaces. The root cause is node's module resolution strategy. Both a boon and a curse ☹️

This PR mitigates the chances of using a transitive dependency by enforcing that each package specify any dependencies in its own package.json (what you would expect). This is accomplished by using adio. A pre-commit check is added to ensure no transitive dependencies are added in subsequent commits.

[TillaTheHun0]

since we are manually bumping package versions for now, this PR will wait on #200 and rebase off it when it is merged.