Ensure that compressed binary used in Amazon Lambda function if present

[geoand]

Fixes: #27208

[patriot1burke]

I don't really understand this bug and how this PR fixes it. Can you elaborate a little? Sorry.

[geoand]

Sure yeah.

The bug report says that the produced function.zip does not include the compressed native binary (the one produced by the invocation of upx by Quarkus during build item after the native binary has been created), but instead includes the original binary produced by GraalVM.

What this PR does is ensure that the step that produces function.zip is always run after the step that compresses the native binary (the use of Optional here is meant to guard against the case where no compression was performed).

Does that make sense?

[patriot1burke]

I guess it makes sense...So you're saying just including the Optional will add the correct binary to the zip?

[geoand]

Yes, exactly. The reason is that it ensures the correct ordering of build steps.

We did the exact same thing in Jib as well