Feature Request: Support different license policies for different scopes/configs

[yogurtearl]

It would be useful to be able to specify different license policies for different scopes/configurations.

e.g. A license is allowed if on the buildScript classpath, but not if it is in production code. Also, a license might be allowed only in test and/or debug, but not allowed in release.

This might happen if the license has terms related to distribution. You might distribute your release artifact, but not the tests.

[JakeWharton]

I planned to support Android variant-based config and Kotlin MPP target-based config.

I was not planning on test or build since those are not subject to any real restrictions. But I'll think about them.

[JakeWharton]

Most of this is possible now thanks to #191 and features like ignoring unused allows. I'll still leave it open as there's probably more to do.