Add check release workflow on CI and CHANGELOG.md

[jtpio]

In preparation for adopting (or at least testing) the Jupyter Releaser: #53

• Add Changelog
• Add check release workflow
• Switch to yarn to simplify the setup
• Use the same version everywhere

[jtpio]

Added two new labels used by github-activity: https://github-activity.readthedocs.io/en/latest/#splitting-prs-by-tags-and-prefixes

[jtpio]

As a follow-up, we can then test a Draft Changelog workflow: https://github.com/jupyter-server/jupyter_releaser#typical-workflow

[jtpio]

#49 was suggesting switching to either yarn or jlpm, and #50 went for jlpm.

Here we change back to yarn to not introduce a new tool (plain yarn is enough) and make the use of the releaser simpler.

[jtpio]

cc @mbektas @fcollonval what do you think about adopting the releaser?

We could then try to go through the typical workflow and cut a new release:

• draft changelog for 3.0.11-3
• draft release
• publish release

Detailed in https://github.com/jupyter-server/jupyter_releaser#typical-workflow

If that works we can then update RELEASE.md with the new instructions.

It it fails somewhere during the process we can always manually publish the new version.

[blink1073]

Nice!

[fcollonval]

what do you think about adopting the releaser?

I'm not against using it. But I'm convinced galata helpers should integrate the core repo as soon as possible.

[jtpio]

But I'm convinced galata helpers should integrate the core repo as soon as possible.

For reference this is discussed in this issue: jupyterlab/jupyterlab#10480

I also think it would be better to move galata there, not sure when that would happen though.

[jtpio]

Let's give it a try and see how it goes.