checkClassUniqueness works with conjure

[iamdanfox]

Before this PR

@dsinghvi reported in #dev-foundry-infra some problems with checkClassUniqueness giving inconsistent results on CI and locally. (We've also had other complaints related to gradle-atlas).

Running the task locally, it seemed no conjure objects were being generated, so the lockfile would be different than if conjure objects did exist.

After this PR

==COMMIT_MSG==
checkClassUniqueness should now behave consistently when asked to analyze configurations that are builtBy other tasks (e.g. gradle-conjure, gradle-atlas)
==COMMIT_MSG==

Possible downsides?

• we don't really know why the current thing isn't working, as it seems like we're doing the recommended thing.

[changelog-app]

Generate changelog in changelog/@unreleased

Type

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

Description

checkClassUniqueness should now behave consistently when asked to analyze configurations that are builtBy other tasks (e.g. gradle-conjure, gradle-atlas)

Check the box to generate changelog(s)

• Generate changelog entry

[svc-autorelease]

Released 3.4.3