…ts with versions

This reverts commit 98ed525.

- Appends tag/version/git describe of both DSOAL and OpenAL Soft to Stable builds, and commit hashes to Development builds.
- Update OpenAL Soft submodule to the latest commit for Development builds, and set to 1.22.1 for Stable builds.
- Include Documentation (licenses, readmes, changelog, etc)
- Set Debug build type for Development builds
- Removed "-latest" from 32+64-bit bundle artifact which became misleading on new builds
- General cleanup

Switched build type from Debug to Release to fix issues with the Development binaries.

- Renamed "Development" and "Stable" builds to untagged and tagged, respectively; which seems more appropriate.
- Removed OpenAL Soft submodule and references.
- Now it clones the latest OpenAL Soft commit (untagged) or the latest release (tagged) during GitHub Actions build.
- Updated some actions and replaced `set-output` command to remove some deprecation warnings, though not all: some actions still need to do the same on their end for the other warnings to disappear.

Also:
- Include revision (commit count) in untagged build filename
- Make sure tagged build uses the most recent *.*.* tag to ignore the makemhr tag

This way a recent OpenAL Soft build is always used, or the latest, if triggered manually.

- Separate release build (DSOAL+HRTF.zip) with a alsoft.ini that has the minimal configuration for HRTF, and the template moved to the Documentation folder (DSOAL.zip will still include the template next to the DLL files)
- Included Version.txt files including repo, branch, version, commit short hash, count and push time
- Versioned files now only found in the workflow artifacts for a cleaner release and to prevent confusion
- Untagged release now includes branch (e.g. latest-master) so that the rewrite branch can get its own releases (didn't use just the branch name in the tag because that makes the GitHub client confuse it with the actual branch when trying to push)
- Updated actions to fix workflow warnings
- General cleanup