Recommend using `cargo info` after the `cargo search` results

[0xPoe]

Problem

Now that we have introduced cargo info', I think it would be useful if we could advise users to use the cargo info' command to inspect the specific crate from the search result.

Proposed Solution

$ cargo +nightly search clap
clap = "4.5.17"                     # A simple to use, efficient, and full-featured Command Line Argument Parser
clap-v3 = "3.0.0-beta.1"            # A simple to use, efficient, and full-featured Command Line Argument Parser
nameless-clap = "3.0.0-beta.2.2"    # A simple to use, efficient, and full-featured Command Line Argument Parser
conf = "0.1.0"                      # A derive-based config parser for CLI args and env parameters
clap-serde = "0.5.1"                # Provides a wrapper to deserialize clap app using serde.
clap-digest = "0.3.0"               # clap and digest integration
clap-nested = "0.4.0"               # Convenient `clap` for CLI apps with multi-level subcommands.
clap-markdown-dfir = "0.2.0"        # Autogenerate Markdown documentation for clap command-line tools
clap-stdin = "0.5.1"                # Provides a type for easily accepting Clap arguments from stdin
clap_derive-v3 = "3.0.0-beta.1"     # Parse command line argument by defining a struct, derive crate.
... and 785 crates more (use --limit N to see more)

note: to see more details about a specific crate, try `cargo info crate_name`

Notes

No response

[epage]

I agree, having a way to bridge users from command-to-command would be useful. We do this today with cargo update -> cargo tree and cargo info -> cargo tree. Knowing how to see more about a search result would be useful.

I would make a couple tweaks

-note: to see more details about a specific crate, try `cargo info crate_name`
+note: to learn more a package, run `cargo info <name>`

[0xPoe]

@rustbot claim

I will add it.