Eslint + GithubActions instead of Travis/Appveyor

[aminya]

• [X] Use Github actions instead of Travis and Appveyor. See the running actions here: https://github.com/aminya/atom-julia-client/actions/runs/68177380
• [X] Add Eslint for js + coffee + json

P.S: no typescript config is in this PR. It's pure JS/Coffee.

[pfitzseb]

Why are Github Actions better than travis?

[aminya]

• It does whatever those travis and appveyors did plus:
• It is faster: ~3min On Github vs ~5min on Travis
• The configuration is easier and gives more flexibility.
• Easier dependency installation
• We can use a custom linter
• We can write custom tests, although not enabled now since spec fails anyways even locally.

https://github.com/aminya/atom-julia-client/blob/github_actions/.github/workflows/ci.yml

[aminya]

This is ready to get merged now.

[aminya]

What's wrong with this? @aviatesk

[aviatesk]

sorry for closing without providing reasons, @aminya I closed since:

• test body itself doesn't seem to work (because it's commented out)
• I don't want to those ESlint stuff to get in

I'm thinking of moving julia-client's CI to use GH actions, but it would be nice if you want to keep work on this:

• remove linting setups
• setup CI in a way that you don't ignore the existing test

Let me know you want to reopen this.

[aminya]

The tests doesn't work locally. This isn't the problem of this PR.

[aminya]

Also, Eslint is configured as just warnings. It doesn't forces anything. It is possible to configure it to use Standard.

https://github.com/standard/eslint-config-standard

The standard way to do online linting is using Eslint framework. Configuration depends on the usecase.