Avoid use of capturing lambdas in JarFile

Capturing lambdas are relatively expensive, and should be avoided if possible. Anonymous local functions, too.

All lambdas used in the interaction between JarFile and ZipFile can be avoided by having ZipFile call a shared secret in JarFile to create a JarFileEntry when appropriate. This removes an allocation per lookup.