When reproducing, use slightly lower limits on heap and stack size so
that minimal changes to fuzz targets, fuzzer and runtime do not cause
memory issues to fail to reproduce.
* [spring-framework] Apply patches in the Dockerfile
Applying patches is part of the sourcecode retrieval, which
we do in the Dockerfile, so apply the patches as part of the
Docker image creation, too.
While here, compile and install _all_ java files rather then
only those ending on "Fuzzer.java", and use a "real" git
checkout, which is required for more "advanced" git features,
most notoriously "log".
* [spring-framework] Use cp over mv in build.sh
Copying the files rather then moving them brings us one step
closer to being re-runable w/o restarting the docker container
* [spring-framework] shadow all our jar files
Also refactor the build.sh and Dockerfile to allow us adding
shadowJars more straightforwardly
* [spring-framework] Also build orm and jdbc, remove commented code
* [spring-framework] Copy all .class files to $OUT/
* [spring-framework] Use install over cp
* [spring-framework] Initial Integration for jdbc
* [spring-framework-jdbc] add copyright headers
Patrice.S