[Feature] Create "api" variants for data file collections

[UpcraftLP]

It would be great to be able to define transitive access transformers / injected interfaces, via something like

dependencies {
	accessTransformersApi("some:dependency")
	interfaceInjectionDataApi("some:dependency")
}

similar to how the java-library plugin creates api configurations for regular dependency scopes.

[lukebemish]

Not sure why these weren't implemented when this system was first put in place from the impl in NG. These should be as simple as having the equivalent of

configurations {
   def accessTransformersApi = dependencyScope("accessTransformersApi") {}
   named("accessTransformers") { extendsFrom accessTransformersApi }
   named("accessTransformersElements") { extendsFrom accessTransformersApi }
}

be set up on the construction of the relevant DataFileCollections, ideally with a DependencyCollector getApi() or something on the DataFileCollection so it can be used from there in the DSL and not just the dependencies block. See how NG does this. This is useful when you consume a dependency as api, and wish to publish the fact that its access transformers or interfaces should be considered part of your own public API -- in that instance, you would do

dependencies {
    api("org.example:gizmo:0.1.0")
    accessTransformersApi("org.example:gizmo:0.1.0")
}