Kepler

Summary: We should probably fix the logic here -- don't download an older version of a module a user already has.

Background:
Doing some sensor-view pre-release testing I:
started Kepler-2.3
switched to reporting-2.3
quit kepler
hacked kepler's module manager configuration.xml to use the test-releases area
restarted kepler
accepted test-releases patches
restarted kepler manually (patch downloader can apparently still fail to restart kepler successfully)
changed to sensor-view-0.9

And at this point, apple-extensions-2.1.0 got downloaded into KeplerData/kepler.modules. This is because the test area didn't have apple-extension-2.1.1. Unless this is something special to do w/ apple-extensions, this means it's possible MM will download old unnecessary modules when the user has a newer version. Except for testing like this, this seems an unlikely problem scenario currently, but there are likely problems lurking should we try using suites composed of modules on different repositories.