Upgrade haskell.haskell to 1.2.0

[djcrock]

https://github.com/haskell/vscode-haskell/releases/tag/1.2.0

[spoenemann]

The haskell namespace has been claimed:
EclipseFdn/open-vsx.org#115

But the extension is still published by our script:
ceccded

@jankeromnes do you remember why it is like that? @jaspervdj would you like to publish the extension yourself?

The extension is currently displayed with a warning because it has an owner, but is still published by our service account:
https://open-vsx.org/extension/haskell/haskell

[jankeromnes]

The haskell namespace has been claimed:
EclipseFdn/open-vsx.org#115

But the extension is still published by our script:
ceccded

@jankeromnes do you remember why it is like that?

Yes. This extension was added to our auto-publish list the day before the namespace was claimed:

@jaspervdj Please publish haskell.haskell 1.2.0 to OpenVSX (e.g. you can do so simply by running npx ovsx publish)

[spoenemann]

Ok, we should remove the entry from here, then.

[jankeromnes]

See also haskell/vscode-haskell#250 (comment)

[jankeromnes]

Seems like OpenVSX-publishing was already set up for haskell.haskell by @bubba.

But it was disabled again in haskell/vscode-haskell@93e7b58 due to a missing OPEN_VSX_ACCESS_TOKEN token in Travis CI: haskell/vscode-haskell#250 (comment)

[jankeromnes]

I guess there is no harm in simply bumping our auto-published version while @jaspervdj and @bubba decide whether they want to take over the OpenVSX publishing.