Warn upon adding a dependency to the containing project to a detached configuration

[tresat]

This targets a merge into #24309, see that PR first.

[tresat]

@bot-gradle test this

[bot-gradle]

I've triggered the following builds for you:

• PullRequestFeedback build

[tresat]

@bot-gradle test this

[bot-gradle]

I've triggered the following builds for you:

• PullRequestFeedback build

[hythloda]

💭 Vague, could we add an example?

[tresat]

I have one just below.

[tresat]

Reading this again, I think maybe you meant an example of the unintuitive behavior, not the usage.

I'll see if I can add a short example.

[big-guy]

What happens if you do this today? I think this might be incomplete due to the way included builds can work.

e.g., it would be possible to have a detached configuration transitively depend on the current project.

[tresat]

After talking to Sterling about this, we've decided not to move forward with this.

We don't want to create another difference in the behavior of detached vs. regular configurations. Eventually, we need to explore the need for detached configurations at all, and if all their use cases can be better handled by regular configurations (perhaps with some additional modifications).

Some relevant issues to consider related to this:
#9894
#6881