add workflow for automatic tag creation

[rem1776]

Description
adds a workflow that grabs the version number from the configure.ac and creates a new tag for releases. It will be triggered whenever configure.ac is modified but will not overwrite previously created tags. The grep command will match both xxx.xx.xx and xxx.xx style version numbers. End result basically ensures each new version number committed to main will have a corresponding tag.

Since my other PR is triggered by a tag (#357) and creates the release draft, once these both go in we'd have a (almost) fully automated release process. A PR containing a change to the version number would be merged in to main, and then we would just have to wait for the actions to run and manually release the created draft.

This kind of thing has potential for script injections, so I used a fairly strict grep command and called github's api directly (rather than using normal git commands). Hopefully that will mitigate any dangers, but any opinions are appreciated.

How Has This Been Tested?
my forks main branch

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• New check tests, if applicable, are included
• make distcheck passes

[ceblanton]

@rem1776 I conflated this with #357 , sorry.. This is the one that might have the -dev in the configure.ac version

[rem1776]

@ceblanton I added the -dev workflow, do we still want the auto-tagging workflow when the version is modified as well?

[ceblanton]

Nice!!

[ceblanton]

@rem1776 Yes, we want both, the -dev workflow and the auto-tagging workflow as well, thanks!