Create a CD pipeline to automate project releases

[traunts]

Create a new GitHub actions workflow to automatically trigger releases in the Data repo on changes to the master or development branches here.

Need to distinguish between "nightly" dev releases and a full release from master in all cases, the two jobs can exist in the same workflow but must execute conditionally.

Requirements:

• Prepare existing build workflows to trigger releases #461
• Confirm project goals regarding semantic versioning. Discussion from Discord
• Create a Release workflow to publish new Source build artefacts #460
• Add proper semantic version comparison to check mod compatibility #468
• Create Automated Release Workflow Cortex-Command-Community-Project-Data#140
  Associated Data Repository issue. Create a new release workflow in the Data repository that pulls the most recently published artefact from this repository to bundle as a release package.
• Create a new job/workflow dependent on the above build/release jobs to trigger the release workflow_dispatch in Data.

Describe Additional Work Required Before Improvement Can be Made

Additional context

my longtime intention has been to do a nice workflow that, on merge to master (and can work for dev for nightly builds too)

1. Builds the exe and appimage in the source repo and stores artifacts for em
2. Does the same for the mod converter I guess
3. Grabs the artifacts from the other repos into the relevant data repo branch and puts together a nice zip with everything (preferably including dlls, but they can remain manual if > needed)
4. Bonus points if the installer repo can grab the data zip and use it to automatically make an installer

...
[RE: Data release steps]

No, it's not too complicated but it is kinda a pain and does take some time. Automating it would be nice haha

1. Make a github release for source, and another for data
2. Make x86 and x64 release exes for windows and appimages for linux
3. Grab a copy of a clean data folder (though often I'm lazy and use mine, making sure to clean it), making sure to include dlls
4. Delete everything that's autogenerated and anything in metagames, then test everything to make sure the game runs and things are fine, then delete any autogenerated stuff again
5. Optionally grab the mod converter (and, in future, the mod manager) and dump it in the folder
6. Zip up the game folder (not rar, for people who don't have rar tools) and upload it to the data release
7. Make the windows installer and also upload it to the data release