Reproducible build

[jasonjkeller]

The weaver loads & caches each instrumentation module by locating the instrumentation module jar and reading in the bytes for the all of the classes contained in the module.

However it appears that the weaver depends on the classes being read in from the JarInputStream in a specific and predictable order, meaning that the instrumentation module jar files need to be generated in a deterministic manner.

This PR modifies the build task for the instrumentation modules so that the resulting jar file always adds files in a reproducible order.

---

One notable example is the jax-rs-1.0 instrumentation, which could fail with a WeaveViolation if the classes weren't read in from the jar (newrelic.jar!/instrumentation/jax-rs-1.0-1.0.jar) in the correct order.

The changes in this PR resulted in the jax-rs-1.0-1.0.jar being consistent between local builds and those published via the github build pipeline and in a manner that resolves the WeaveViolation

---

Helpful reference: https://dzone.com/articles/reproducible-builds-in-java

[jasonjkeller]

AIT run: https://javaagent-build.pdx.vm.datanerd.us/view/All/job/JavaAgent_PR_AIT/47/