Adjust mechanism of resolver conflict detection
Adjust mechanism of resolver conflict detection

Warn when publish resolver and dependency resolvers have same name but different access mechanism.
Multiple resolvers having same name as well as same access mechanism (i.e., equality matching) isn't
usually a problem. A common scenario for this would be Maven based resolvers with exact (http based)
same access mechanism. Also see #367, #363

pocketberserker/sbt,xeno-by/old-scalameta-sbt,jamesward/xsbt,jroper/sbt,dyx/sbt,olove/xsbt,jaceklaskowski/sbt,gilt/xsbt,jamesward/xsbt,xuwei-k/xsbt,jamesward/xsbt,xeno-by/old-scalameta-sbt,jkinkead/sbt,mdedetrich/sbt,olove/xsbt,mdedetrich/sbt,dyx/sbt,harrah/xsbt,xuwei-k/xsbt,xeno-by/old-scalameta-sbt,mdedetrich/sbt,olove/xsbt,jroper/sbt,sbt/sbt,som-snytt/xsbt,jamesward/xsbt,Duhemm/sbt,corespring/sbt,jaceklaskowski/sbt,mdedetrich/sbt,jkinkead/sbt,harrah/xsbt,Sciss/sbt,twitter-forks/sbt,xeno-by/old-scalameta-sbt,xeno-by/old-scalameta-sbt,twitter-forks/sbt,mdedetrich/sbt,jroper/sbt,dansanduleac/sbt,sbt/sbt,jkinkead/sbt,jroper/sbt,Duhemm/sbt,jkinkead/sbt,xeno-by/old-scalameta-sbt,sbt/sbt,xuwei-k/xsbt,twitter-forks/sbt,jasonchaffee/sbt,twitter-forks/sbt,Duhemm/compiler-bridge,harrah/xsbt,gilt/xsbt,sbt/sbt,mdedetrich/sbt,jaceklaskowski/sbt,xuwei-k/xsbt,dyx/sbt,jaceklaskowski/sbt,xuwei-k/xsbt,twitter-forks/sbt,gilt/xsbt,jroper/sbt,jamesward/xsbt,dyx/sbt,sbt/sbt,harrah/xsbt,olove/xsbt,dyx/sbt,jaceklaskowski/sbt,harrah/xsbt,harrah/xsbt,sbt/sbt,adriaanm/sbt,sbt/sbt,pdalpra/sbt,mdedetrich/sbt,gilt/xsbt,jkinkead/sbt