`DependencyWriter` seems to examine unresolved configurations

[yevhenii-nadtochii]

We see the following warning when building text module:

The project uses several versions of `io.spine.validation:spine-validation-java-runtime` dependency.
module: text, configuration: implementation, version: 2.0.0-SNAPSHOT.61
module: text, configuration: implementation, version: 2.0.0-SNAPSHOT.40

The mentioned library has two versions in the same module and configuration.

In the build file, this library is forced to prevent a conflict:

    all {
        resolutionStrategy {
            force(
                spine.base,
                spine.validation.runtime, // This one.
            )
        }
    }

And build scan confirms it:

But DependencyWriter still sees two versions and uses deduplication to prevent several versions of a single library in POM. In this case, it shouldn't have happened. DependencyWriter is meant to examine already resolved configurations, and only then deduplicate, if needed.