Update guava to 33.2.0-jre

[scala-steward-asf]

About this PR

📦 Updates com.google.guava:guava from 33.1.0-jre to 33.2.0-jre

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "com.google.guava", artifactId = "guava" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.guava", artifactId = "guava" }
}]

^{labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1}

[raboof]

link validator failure is unrelated:

## HTTP failure response
`[https://web.archive.org/web/20180114133958/http://roestenburg.agilesquad.com/2011/02/unit-testing-akka-actors-with-testkit_12.html`](https://web.archive.org/web/20180114133958/http://roestenburg.agilesquad.com/2011/02/unit-testing-akka-actors-with-testkit_12.html%60) status 429 Too Many Requests
 - testing.html

I wonder if we should remove the link validator from PR validation and instead run it nightly/weekly to monitor for longer-term failures?

[pjfanning]

I strongly favour taking link validation off the main builds and have it run as a separate standalone run. It is just far too brittle.

[raboof]

I strongly favour taking link validation off the main builds and have it run as a separate standalone run. It is just far too brittle.

filed #1309