Update dependency graph in README to show dependencies, peerDependencies, and devDependencies

For instance, `@metamask/composable-controller` technically includes `@metamask/address-book-controller`, `@metamask/assets-controllers`, and others in its list of development dependencies because it uses them for tests, but none of these are actually needed to use the controller itself, so this would be helpful to know when looking at the big picture.

It would also be helpful to know which controllers have peer dependencies on other controllers to assist with upgrading clients.

Start by reviewing the existing dependency graph in the README and the repository's current dependency information. The update is complete when the graph distinguishes dependencies, peerDependencies, and devDependencies, including controller-to-controller peer dependencies, so client upgrade impact is clear.

Written by the indexing model from the issue text.