chore: update dependencies

[fabianhjr]

Tested locally via ./gradlew check

Security/CVEs of direct dependencies:

• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908 (Guava)
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11050 (Java-WebSocket)

Scalatest upgrade required a a small rename/import change of

import org.scalatest.FunSuite to import org.scalatest.funsuite.AnyFunSuite

as per https://www.scalatest.org/release_notes/3.1.0

[magnus-madsen]

Thanks-- not sure if we can upgrade Scala just yet because of #4916

[magnus-madsen]

How long does gradlew clean jar take on master versus with your PR on your machine?

[fabianhjr]

About same time around 60s

[magnus-madsen]

Is that because the Scala version is not touched?

[fabianhjr]

The scala version remained at 2.13.5 yes.

I could include the dependeny tree on the description.

[magnus-madsen]

In any case, we are usually handle upgrades much more "one at a time" to prevent regressions.

I think it would be sensible to break this PR into a few smaller ones that can be merged on at time:

• One for Guava.
• One for Java WebSocket.
• One for ScalaTest with the changes.

[magnus-madsen]

We usually do small changes and then look arewefast.flix.dev and wait for our users to report back.

[fabianhjr]

Will open separate merge requests and leave this one as a meta/draft one.

[magnus-madsen]

Will open separate merge requests and leave this one as a meta/draft one.

Sounds good, but don't do them all. Let us just focus on Gradle, ScalaTest, and the ones with CVEs.

Also I will have to merge them at 1 per hour due to arewefast.

[magnus-madsen]

Superseded by other PRs.