chore(java): provide tar.gz artifact in releases

[bcmedeiros]

Solution for #2536

[wpessers]

@bcmedeiros in the workaround you mention in that issue you explicitly add the --chmod=755 arg. I think that something similar would still be required when trying to use this archive in your Dockerfile directly.

It looks like gradle's default file permissions make it so our wrapper scripts are all 644 (not executable)... When we use them inside a lambda layer there's no issue because aws lambda seems to automatically do some sort of normalization of permissions when extracting layer contents.

I think we can make the script files in the archive executable though, look at this example from gradle docs: https://docs.gradle.org/current/userguide/working_with_files.html#using_copyspec_dir_permissions
I'd suggest doing something similar to configure 755 permissions for our scripts, in that copySpec block.

[bcmedeiros]

The tar.gz package will preserve the original permissions of the file as committed in git, while zip will not, that's probably why the workout was needed in my example.
I'm pretty sure I tested the tar had 755 scripts, but I'm on my phone now, I can't check how the files are in git.
Anyway, we could apply your suggestion, it won't cause any harm.

[bcmedeiros]

you were right, @wpessers, Gradle's from("scripts") normalizes the file permissions. I've accepted your proposed changes.

[tylerbenson]

Thanks for taking care of this!