crater: drop implied bound with non-universal region

[tiif]

Implied bound could wind up having non-universal region and this behavior is kind of baffling to me. Currently, dropping implied bound with non-universal region won't break any ui test, so I am opening this PR to run crater to see if it breaks anything in the ecosystem.

cc @lcnr

[tiif]

@bors try

[rust-bors]

☀️ Try build successful (CI)
Build commit: e3d12f3 (e3d12f3322cb00126b2208c6b9df3ac4467951f5)
Base parent: 1af98b7 (1af98b7cdf86932b76182a387f52f1be6f0c1be0)

[tiif]

@craterbot check

[craterbot]

👌 Experiment pr-159706 created and queued.
🤖 Automatically detected try build e3d12f3
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

[craterbot]

🚧 Experiment pr-159706 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

[craterbot]

🎉 Experiment pr-159706 is completed!
📊 2 regressed and 5 fixed (1041933 total)
📊 5785 spurious results on the retry-regressed-list.txt, consider a retry¹ if this is a significant amount.
📰 Open the summary report.

⚠️ If you notice any spurious failure please add them to the denylist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

Footnotes

1. re-run the experiment with crates=https://crater-reports.s3.amazonaws.com/pr-159706/retry-regressed-list.txt ↩

[lcnr]

The fact that these exist is quite dubious. Interesting that they don't matter for any crate, can you summarize the tests where we encounter these regions?