When a Configuration is copied, any before and after resolve actions
that are registered with its ResolvableDependencies are also copied
over. This means that, when a copied configuration is resolved the
resolution actions may be called on a ResolvableDependencies instances
that isn't the one to which they were added.

Previously, the above-described Gradle behaviour would result in
BootJar accessed the ResolvedConfiguration of a Configuration that may
not have yet been resolved. At best this would trigger Configuration
resolution and at worst it would fail. A failure could occur if the
configuration had been copied so that it could be made resolvable.
The afterResolve action would then try to access the
ResolvedConfiguration of the original Configuration. This would trigger
a resolution attempt that fails due to the original configuration being
marked as unresolvable.

This commit updates the afterResolve action in BootJar to check that
the ResolvableDependencies with which it is called matches the
ResolvableDependencies with which it was original registered. Only
when the two match, and therefore the configuration has actually been
resolved, does processing proceed.

Fixes gh-24072

Closes gh-24090

Closes gh-24089

Closes gh-24088

Closes gh-24087

Closes gh-24086

Closes gh-24085

Closes gh-24084

Closes gh-24083

Closes gh-24082

Closes gh-24081

Closes gh-24080

Closes gh-24079

Closes gh-24078

Closes gh-24077

Closes gh-24069

See gh-24035

See gh-24034

Closes gh-24067

Closes gh-24066

Closes gh-24062

Closes gh-24060

Closes gh-24045

Closes gh-24059

Closes gh-24058

Closes gh-24057

This commit makes sure to use the most specific getter if more than
one candidate exists.

Closes gh-24002

Closes gh-23955

Closes gh-24056

Closes gh-24055

See gh-24053

See gh-24052

See gh-24041

Closes gh-24053

Closes gh-24052

Fixes gh-24041