simplify top-level repo directories?

A few people (myself included) have observed that this repo has an overwhelming number of top-level directories. It might help new developers better find stuff if there were a bit more structure.

Some ideas, possibly terrible:

• Maybe the contents of "deploy" (which I think only houses thing-flinger) could be merged into "dev-tools"? What do you think @andrewjstone?
• Maybe the contents of "package" could go into "dev-tools" too?
• Maybe these could be grouped together (in directories; I'm not suggesting changing the crate structure at all):
  • gateway: gateway, gateway-cli, gateway-test-utils, [gateway-client]
  • installinator: installinator, installinator-artifactd, installinator-common, [installinator-artifact-client]
  • tufaceous: tufaceous and tufaceous-lib
  • wicket: wicket, wicket-common, wicket-debug, wicketd, [wicketd-client?]
  • clients: bootstrap-agent-client, ddm-admin-client, dpd-client, dns-service-client, nexus-client, oxide-client, oximeter-client, sled-agent-client, gateway-client (if not above), wicketd-client (if not above), installinator-artifact-client (if not above)

I'm not familiar with most of these components and I'm basically just going by the names. If you are familiar with these and have feelings either way, speak up!

Also, if folks have better suggestions for organizing things, that'd be good, too.

Start by reviewing the repository’s top-level directories, especially deploy, package, and dev-tools, then compare the proposed gateway, installinator, tufaceous, wicket, and clients groupings. The issue asks for discussion rather than naming a chosen structure, so done would require maintainer agreement on an organization plan before any changes are made.