Upgrades gradle wrapper to the latest version

[gsheasby]

Started as a copy of #2824... became a massive hunt for broken and outdated dependencies.

Goals: eliminate dependency conflicts across the repo

Implementation description

• Upgrade nebula and sls-packaging to their latest versions
• Apply the correct force strategy to clear out the duplicated dependencies
• Add timelock.props (and later qos.props) to make explicit the special dependencies used by Timelock and QoS
• Fine-tune the dependency bumps to correct test failures

The root cause of the test failures was that Timelock and QoS each have a special set of dependencies. QoS was simply using Timelock's old, kind of janky dependency specification logic. QoS needs some of the same custom dependencies as Timelock, but not all. This is now made explicit via qos.props and timelock.props

Future work

• There's still some special dependency logic in versions.gradle - we should unify this with the props files so that dependencies are specified in one place.
• @iamdanfox suggested that we can/should get rid of the troublesome *.lock files entirely, but this is beyond the scope of this PR
• Upgrade baseline/errorprone (we're on v13, v18 is available)
• The baseline/errorprone upgrade flagged a couple of errors in PTExecutors.java; I'll open a separate PR for this after this merges, possibly as part of MMM next week.

---

This change is 

[jeremyk-91]

Hmm. The change looks alright (verified it is the same as the one excavator-bot tried to do), but it seems that something might have changed in gradle-sls-packaging or the nebula publishing plugin perhaps:

[00:00:17] FAILURE: Build failed with an exception.
[00:00:17] 
[00:00:17] * Where:
[00:00:17] Script '/home/ubuntu/atlasdb-internal-testing/gradle/publish-jars.gradle' line: 4
[00:00:17] 
[00:00:17] * What went wrong:
[00:00:17] A problem occurred evaluating script.
[00:00:17] > Failed to apply plugin [id 'com.jfrog.artifactory']
[00:00:17]    > Could not create task of type 'ArtifactoryTask'.
[00:00:17] 
[00:00:17] * Try:
[00:00:17] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
[00:00:17] 
[00:00:17] BUILD FAILED
[00:00:17] 
[00:00:17] Total time: 17.151 secs

[gsheasby]

@jeremyk-91 I'll own investigating what's going on here.

[gsheasby]

There's a dependency conflict somewhere in the buildscript dependencies, relating to guava:

Caused by: java.lang.NoSuchMethodError: com.google.common.collect.ArrayListMultimap.create()Lcom/google/common/collect/ArrayListMultimap;

However, I can't run depencencyInsight because I hit the same roadblock!

[gsheasby]

Reassigning to @jeremyk-91 for review. However, this PR has high potential for merge conflicts, and there's also the danger that someone will, in the meantime, introduce something that will make the new dependency-recommender version freak out.

[jeremyk-91]

I've sanity checked the changes - looks reasonable, and the new structure of dependencies for QoS and TimeLock is considerably more readable.

Agree that the points under 'future work' should indeed be future work - this is already a fairly large PR.

[jeremyk-91]

Nice.

[jeremyk-91]

nice, no idea we used commons-lang for these