baseline-exact-dependencies stops resolving compileOnly

[dansanduleac]

Before this PR

baseline-exact-dependencies was trying to resolve compileOnly and annotationProcessor in order to determine dependencies that should be ignored because they are "source-only".
This now breaks with 3.5.0 / #1254 because we've banned resolving compileOnly directly.

After this PR

==COMMIT_MSG==
Fix baseline-exact-dependencies to no longer resolve compileOnly directly.

Instead, we create another configuration extending from compileOnly, which we tell to resolve only compile variants (so they'll be guaranteed to be the same variants as what's resolved by compileClasspath).
Also, excluding annotationProcessor was bogus because annotationProcessor is entirely independent from the other java configurations and doesn't end up in compileClasspath at all.
==COMMIT_MSG==

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

Type

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

Description

Fix baseline-exact-dependencies to no longer resolve compileOnly directly.

Check the box to generate changelog(s)

• Generate changelog entry

[svc-autorelease]

Released 3.5.1