RATIS-2226. Enable Develocity local build cache

[adoroszlai]

What changes were proposed in this pull request?

The [Develocity] Build Cache speeds up your builds by reusing outputs from any previous build
[The] local Build Cache [...] allows other subsequent builds on the same machine to reuse the outputs whenever they execute a goal with the same inputs.
(source)

This PR enables cache for local builds, but not for CI builds.

Develocity can also publish build scans (information about build/test runs), which could be enabled in a follow-up task.

https://issues.apache.org/jira/browse/RATIS-2226

How was this patch tested?

First build with cache (can be reproduced later by adding -Ddevelocity.cache.local.enabled=false):

$ ./mvnw -Prelease -DskipTests clean verify
...
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  41.167 s
...
[INFO] 417 goals, 417 executed

Re-build uses output from build cache for several steps:

$ ./mvnw -Prelease -DskipTests clean verify
...
[INFO] --- javadoc:3.3.2:jar (module-javadocs) @ ratis ---
[INFO] Loaded from the build cache
...
[INFO] --- compiler:3.10.0:compile (default-compile) @ ratis-proto ---
[INFO] Loaded from the build cache, saving 1.854s
...
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  14.471 s
...
[INFO] 417 goals, 366 executed, 51 from cache, saving at least 23s

As a follow-up, we may check if other builds steps (e.g. jar, shade, etc.) can be tweaked to allow caching.

CI build:

[INFO] 436 goals, 436 executed

https://github.com/adoroszlai/ratis/actions/runs/12453457990/job/34763583099#step:5:3079

[szetszwo]

+1 the change looks good.

[adoroszlai]

Thanks @szetszwo for the review.