Silently disable the linter if its command does not exist

More details about this bug: AtomLinter/linter-shellcheck#3 

I resolve this bug by silently disable the linter if its command does not exist. I think there should be a better way, for example, pop up a dialog to let the user choose disable the linter, or specify the linter command path manually.

---

***The current commit (5c26e8e) resolve the performance issue. Please review.***

No, the original error is not silent, it will pop up the dev console and interrupt the normal input. You can test it with setting a wrong bin path for some linters.