Update dependencies

[JM-Lemmi]

Hey,

I have updated all the dependencies of the project with yarn upgrade. These changes have been tested on our fork and I could not find any incompatibilities.

On our fork I also moved the containers to rolling releases instead of fixed releases (to make keeping the images up to date easier without code changes) as well as removing the eslint graphql plugin, as it has a fixed vulnerable dependency as well as being deprecated by the authors. If you also wan't those commits just lmk and I'll pick the to this branch.

Cheers!
Lemmi

[XeR]

Hello, thanks for your interest in CTFNote.

I have updated all the dependencies of the project with yarn upgrade.

We did the same on dev a few days ago. (#143)
It's not on main yet because the vulnerabilities do not impact us. (Feel free to prove me wrong :-) )

I changed your PR to rebase to dev instead of main.

On our fork I also moved the containers to rolling releases instead of fixed releases

What is the point ? New features usually don't code themselves.
On the other hand, this might introduce breaking changes without anybody noticing.
I'm not feeling like gambling with other people's infra. I think we'll keep upgrading Dockerfile by hand.

as well as removing the eslint graphql plugin, as it has a fixed vulnerable dependency as well as being deprecated by the authors

Did you replace it with the recommended alternative, or did you just drop it ? cf. #144
Since this is dependency only used by devs, I want to have @JJ-8, @B-i-t-K and @SakiiR's input before touching this.

FTR, the vulns in question are:
https://www.npmjs.com/advisories/1004946 (ReDoS, in 3 dependencies)
https://www.npmjs.com/advisories/1005162 (ReDoS)
https://www.npmjs.com/advisories/1006899 (Cookies/Authorization headers get sent after a 30x to a different domain, not sure how this makes sense for a linter)

[JJ-8]

I am perfectly fine with dropping the graphql plugin if it removes vulnerabilities. Replacing is also great, but I don't mind.