Revise release script

[bocchino]

• Improve diagnostic messages.
• Improve validation of release archive. Use diff instead of size estimate to check correctness.
• Revise the directory structure in the release archive. On my Mac, I noticed that we were giving absolute paths starting with / to tar. But these paths are meaningless in a release tar ball. My Mac was warning about it.
• Bump the GraalVM version to 22.3.0. This also fixes the problem with the missing trace info.
• In GraalVM 22.3.0, the trace info that we added by hand caused a warning, so I deleted it.
• Delete the code that runs all the JVM unit tests and captures the trace. Since we are checking the trace into the repo, and it seems brittle to changes in FPP and/or GraalVM, the procedure will be to run the trace manually, verify that everything is working, and commit any changes to the trace before submitting a release to GitHub.
• Revert the GraalVM README to what we had in the previous release. Hopefully, with the latest GraalVM, we won't have to hand-edit trace files.
• Use gtar instead of tar on Mac OS -- tar does not work properly.
• Switch from ubuntu-latest to ubuntu-18.04 for compatibility.
• Add and document an FPP_NATIVE_IMAGE_FLAGS configuration variable.

[bocchino]

The archive creation failure appears to be a known issue with the Mac OS virtual environment. See https://github.com/actions/runner-images/issues/2619.

[bocchino]

The archive creation failure appears to be a known issue with the Mac OS virtual environment.

Attempting to fix by using gtar if available.

[bocchino]

I successfully got release v1.1.0a6 through the GitHub build process. Whew!

https://github.com/fprime-community/fpp/releases/tag/v1.1.0a6

@tiffany1618 This release should be good to test with. I used it to build F Prime on your branch.

[LeStarch]

@bocchino we should switch the runner to ubuntu-18.04 for similar reasons to using the latest macOS. In the long-term I do not think this method of distributing FPP is sustainable as the runners to build these tools are deprecating faster than the platforms we need to support.

[LeStarch]

Note: building on 18.04 has kernel version 4.15 which is old enough for our Redhat customers.

[LeStarch]

@bocchino also, why not bump to 22.3.0?

[LeStarch]

I might also add an argument for extra native-image flags. For example, the issue I was seeing on the redhat was /tmp was mounted as noexec. Thus I needed to supply an alternative /tmp using -H:TempDirectory=/path/to/something/executable.

[bocchino]

I might also add an argument for extra native-image flags.

Done.

[LeStarch]

I ran on 22.3.0 last night and everything went fine.