Aliasing `cats.kernel.Order` in `cats._` package leads to ambiguous reference error

Im using cats.kernel.Comparison, which isn't aliased and so requires import cats.kernel. I generally have a wildcard import policy for cats packages, which leads to:

reference to Order is ambiguous;
[error] it is imported twice in the same scope by
[error] import cats.kernel._
[error] and import cats._

IMO, there are two sustainable options:

• Policy to alias the entire public API of cats.kernel._ into cats._. Implies PRs etc aren't complete until the alias is added.
• Don't alias anything. People have to import both explicitly to work with cats.

There is a third option, which is people are supposed to cherrypick-import non-ambiguous names from kernel as needed, but IMO thats a minefield we should avoid creating in the first place.

(apologies if I missed earlier discussion of this issue, I struggle to keep up with everything cats. please cross-link any prior context)

Start by reviewing the cats.kernel and cats._ public import surfaces, especially the handling of Order and Comparison, then look for earlier discussion of the two proposed aliasing policies. Done requires an agreed policy and a clearly scoped implementation plan; the issue does not identify files or tests to change.