Merge #6790

6790: Fix multiple source warning messages from `error` to `warn` r=greysteil a=jlw

### What was the end-user problem that led to this PR?

I've been working on a few repos for most of this year that use a privately-hosted gem with the same name (but completely different purpose) as a gem hosted at rubygems.org - whenever I start with a clean copy and `bundle install` for the first time, I am presented with a warning in red that the gem was found in multiple sources. The red text makes me think that something went wrong, even though bundler did exactly what I wanted it to do.

The user experience is wrong - a warning should not be red.

### What was your diagnosis of the problem?

When I looked at the source, I saw immediately that the warning was using `Bundler.ui.error` instead of `Bundler.ui.warn`.

This is a bug fix with a limited lifespan - after setting up a local copy of bundler I see that 2.0's handling of multiple sources A) is smarter and bypasses the error in most of the repos where I saw it with bundler 1.x; and B) fails early with a different error message in the remaining repos.

### What is your fix for the problem, implemented in this PR?

The fix is simply switching to `Bundler.ui.warn` in this case.

### Why did you choose this fix out of the possible options?

_I didn't see any other possible options._


Co-authored-by: Jeremy Weathers <jeremy@codekindly.com>

0 files changed, 0 insertions, 0 deletions