Consider fine-tuning DSL for ABI reporting

Currently the plugin lets users declare that "I don't care about used transitive dependencies, don't bother me about them." I wrote the code a while ago, but it is my recollection that this suppresses all such advice, period. This can be an issue if the advice says "add dependency X to the `api` configuration." That's an issue because it's really important for library authors to get their `api` declarations correct so as to not inadvertently break users. I think it's worth looking at that to see if we can (optionally or by default) not suppress api-related advice.

No file or test is named. Start by tracing the plugin's DSL handling for suppressing used transitive-dependency advice, then determine how ABI-related advice for the `api` configuration should be treated. Done means the chosen optional or default behavior preserves relevant `api` advice while retaining the intended suppression elsewhere.

Written by the indexing model from the issue text.