Confusing readme: The crate was renamed from `cargo-deny` to `cargo-caps`(?)

Earlier in the readme:

> cargo-caps check will run cargo build and then analyze the linker symbols of each built library. Based on these symbols cargo-caps will then infer capabilities of each library.

Later

> cargo-deny can tell whether or not a library can use the network, but not to where it connects.

Read the README passages describing cargo-caps and cargo-deny and compare the names and behavior they attribute to the crate. Clarify the naming throughout the README so the project name and described capabilities are consistent, then verify that both quoted sections no longer conflict.

Written by the indexing model from the issue text.