[Feature] Adding filters to yarn explain peer-requirements

[aqeelat]

• I'd be willing to implement this feature (contributing guide)
• This feature is important to have in this repository; a contrib plugin wouldn't do

Describe the user story

As a developer, running yarn explain peer-requirements generates a lot of output that makes it hard to investigate missing dependencies. For example, it says a package I'm importing does not provide type stubs to another package it is importing, which does not add value to me.

Describe the solution you'd like

A way to filter out the results with flags such as:

• -t, --include-types: This includes the types packages (p05130 → ✓ socks-proxy-agent@npm:8.0.3 doesn't provide @types/supports-color to debug@npm:4.3.6 [3374e]). It should be disabled by default.
• -m, --only-missing: This filters out any line with a green check mark.
• '-p, --include-optional`: This includes optional peer dependencies that are not provided by third party libraries to their dependencies.
• '-l, --level $level': This controls how much nesting should be analyzed. (mypackage -> x -> y -> z -> a -> b) I think we rarely need to go beyond 2 levels.

We should add telemetry on these flags to analyze how users are using them and then we can decide if we need to make them disabled/enabled by default, or if we can remove the flag and bake-in the filters.

Describe the drawbacks of your solution

Describe alternatives you've considered