Increment Version and Release Installers

[jadeandtea]

Description

The previous version of these two github actions relied on the ability to commit directly to master, which is not possible on the main repository.

The Increment Version Action must be manually triggered, which will create a PR that starts with "increment-version-number-". When the PR is merged successfully, the Release Installers action runs and creates a draft release with the three installer zips attached.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Enhancement (improvement to an already existing feature)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

This works as descrbied above in my fork.

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes