Make scry resilient to compiler errors

[faustinoaq]

After discussing with @RX14 on #104 I got the idea of modify the crystal compiler to ignore build errors and get implementations, symbols, hover even if you have a diagnostic with 200+ problems.

This way we can work pretty much like C# and Java IDEs :tada:

See: https://github.com/crystal-lang-tools/scry/issues/104#issuecomment-386895054

[faustinoaq]

As I said on https://github.com/crystal-lang-tools/scry/issues/104#issuecomment-386895054. I guess ignoring build errors inside crystal compiler is a bit complex. So I think we can try to fix the analyzed code or comment out the lines with errors to ensure crystal tool to return some non-diagnostic response.

[kingsleyh]

This is still an issue:

[Error - 10:14:56 AM] A error was found while searching implementations
Unexpected char 'W' at 1:1
Warning: Gzip is deprecated, use Compress::Gzip