Create source code packages by adding release tags

[dearblue]

According to the GitHub blog, files by git archive are not guaranteed to have checksum persistence.
It is also stated that the archive file at this time is stable in bytes, but that this may change in the future.

---

Creating a tag in the format "x.y.z" will cause a build for release and the source code will be published in the form of a tarball.
If the tag name contains "-rc", it will be published as a "pre-release".
Release notes are taken from the contents of the NEWS file.

For GitHub Actions logs and previews, please follow the URL below (this repository will eventually be removed).

• For version "192.168.0.1-rc"
  • https://github.com/dearblue/SANDBOX1/actions/runs/7348227811
  • https://github.com/dearblue/SANDBOX1/releases/tag/192.168.0.1-rc
• For version "192.168.0.1"
  • https://github.com/dearblue/SANDBOX1/actions/runs/7348228299
  • https://github.com/dearblue/SANDBOX1/releases/tag/192.168.0.1

[dearblue]

In the future, you may be able to do the following
However, this does not necessarily mean I will do it.

• Files required as a package can be generated automatically in advance.
  For example, in the future, it will no longer be necessary to include "mrbgems/mruby-compiler/core/y.tab.c" in the repository.
• In the future, even when git submodules are used to incorporate other repositories, the release package can be reliably included.
• Automate the provision of pre-built binary packages.
  MSVC 32/64, mingw32, mingw32-x64, etc.?
• It may be possible to provide source code packages that cannot be modified at build time but do not require Ruby.
  In this case, we might just generate a presym-related file and a "Makefile" or "CMakefile" file?
  This might be a solution for Support in Vcpkg #6016.

[dearblue]

The main change is that it no longer fires in the clone repository.