[WIP] Generate a test dependencies file to support unit tests in entitlements

[jdconrad]

Example file output:

{
    "name": "lang-painless",
    "locations": [
        {
            "class": "Location.class",
            "module": "module-goes-here"
        },
        {
            "class": "org/objectweb/asm/tree/analysis/Analyzer.class",
            "module": "module-goes-here"
        },
        {
            "class": "org/objectweb/asm/AnnotationVisitor.class",
            "module": "module-goes-here"
        },
        {
            "class": "org/antlr/v4/runtime/ANTLRErrorListener.class",
            "module": "module-goes-here"
        },
        {
            "class": "org/objectweb/asm/tree/AbstractInsnNode.class",
            "module": "module-goes-here"
        },
        {
            "class": "org/objectweb/asm/util/ASMifier.class",
            "module": "module-goes-here"
        },
        {
            "class": "org/objectweb/asm/commons/AdviceAdapter.class",
            "module": "module-goes-here"
        }
    ]
}

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[prdoyle]

We could reduce redundancy by mapping just package names to modules, instead of every individual class. That should make the file much smaller.

[prdoyle]

Jack pointed out that this already has just one entry per jar/directory.

In that case, I wonder if the structure should include that jar/directory info, if only for troubleshooting. Even if we don't need it to make our use case work, it could be easier for humans if the jar/directory is present in the file.