Automate release tarball creation

[ronawho]

There have been generated files included in the last several release tarballs. I believe this is due to manually creating the tarball from a directory where autogen/configure has been run.

I have caught this a few times while upgrading versions, though I missed some when upgrading to the 1.16 release in chapel-lang/chapel#17229. In 1.16 there were a lot of files in an installed directory. There were different files for 1.17 but I believe we caught all those.

Offline @janciesko and I had discussed automating the process to avoid issues like this. There are probably github actions that would let you automate creating your tarball. With a quick search https://github.com/marketplace/actions/create-release seems promising, but there are probably others.

(We discussed this offline a while back, but this recently bit us in Homebrew/homebrew-core#91257 (comment) so I wanted to create an issue before I forgot.)

[olivier-snl]

Thanks @ronawho . This is an important issue to address.

[janciesko]

This script [1] runs autotools, generates the configure script and replaces linked files by actual files required during ./configure.
The next step would be to trigger this script on a GitHub Actions event when a tag is pushed.

[1] #115

[ronawho]

Just noting the package.sh script seems to be producing pretty clean tarballs the last 2 releases, so I'd have no problem closing this. Your call if it's worth the additional work of figuring out a github action.