Detect and fix when a dependency is in both implementation and api

There's the simple case of the same coordinates declared in both configurations.

The case I just fixed was more complex as it was two different version catalog entries:
```toml
[versions]
foundationLayout = "1.8.3"

[libraries]
compose-bom = { module = "androidx.compose:compose-bom", version = "2025.08.00" }
composeUi-foundation-layout = { module = "androidx.compose.foundation:foundation-layout" }

androidx-foundation-layout = { group = "androidx.compose.foundation", name = "foundation-layout", version.ref = "foundationLayout" }
```
```groovy
dependencies {
api platform(libs.compose.com)
api libs.composeUi.foundation.layout

implementation libs.androidx.foundation.layout
}
```

No source file or test is named. Start by reproducing the shown Gradle version-catalog setup, including the two aliases for foundation-layout, and inspect the dependency analysis advice. Done means the plugin detects the duplicate implementation/api dependency even when the aliases and versions differ, then reports or fixes it consistently.

Written by the indexing model from the issue text.