Potential dependency conflict when the version of a dependency is changed on zeppelin interpreters

Potential dependency conflict when the version of a dependency is changed on zeppelin interpreters.

For example, if you have the dependency "dependency:0.1", and you change the version to "dependency:0.2", the old dependency does not get removed from the folder where zeppelin stores the dependencies jars, causing potential dependency conflicts.