Browser extension silently breaks instead of saying "repo not on your sourcegraph instance"

Created by: slimsag

I observed a user try to use the browser extension on some private repositories they had not added to their Sourcegraph instance yet. Instead of being told anything, the browser extension just "did not work" and it was not clear at all why.

If we can make requests to the instance but the repository doesn't exist, we should probably indicate that to users?