vim: use my own multiple-cursors repository to avoid conflicts with Neocomplete

Using a very dirty workaround in a fork of vim-multiple-cursors I can avoid the
current issue #12 that causes a conflict between this plugin and neocomplete.