Fix to local semver issue#12

I have a potential fix to resolve #12...

In `./lib/semver.js#resolveSemverRemotely,` if the `local` remote findst the target component (`name` param) in `components` it volunteers as the `remote` on which other versions of the same component can be sourced... and of course this may not be the case...

So the PR does exactly as before, except if the semver is not resolved by the `local` remote, then it affords the other branch remotes an opportunity to resolve the `ref`.

@jonathanong, @dominicbarnes I'd like to merge these changes to master... Please let me know if you see any gotchas...