baseline-class-uniqueness is updated by ./gradlew --write-locks

[iamdanfox]

Before this PR

Currently running ./gradlew --write-locks will not actually update people's baseline-class-uniqueness.lock file. (Amusingly I had this code locally, I just had forgotten to push it).

This is bad because many of our excavators rely on just running --write-locks after touching plugins, so they're currently red (e.g. onelogger on build2).

After this PR

==COMMIT_MSG==
Running ./gradlew --write-locks will now update the baseline-class-uniqueness.lock file.
==COMMIT_MSG==

Possible downsides?

The --write-locks invocation is quite a frequently invoked thing, and this makes it a little slower :/

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Running ./gradlew --write-locks will now update the baseline-class-uniqueness.lock file.

Check the box to generate changelog(s)

• Generate changelog entry

[svc-autorelease]

Released 2.48.1