It's enough to build the win64 companion on PRs for testing, and this keeps the win32 builds from going stale, and may also keep it's build cache form from being cleared.
* fix: Prevent potential wordsplitting of variables
* chore: Remove need for separate cpn 32bit script
* Build script tag/branch/PR auto-detection
* Teach companion about VERSION_TAG
* Update some constant names
* Only one companion build script
* Actually use `VERSION_SUFFIX` in about screen 🤦
* Add space
* Remove line that was only for testing 32bit build
* Remove hyphen between win and bits
* Show codename in Settings -> Version
* cpn: Only show codename on tagged versions
* Update about screen also
* Double quotes around codename on colorlcd
* Update copyright year
* About screen should use VERSION_TAG when set
These invocations will all cause bugs when pwd returns something that
can be interpreted by bash, the most common case being a folder
with whitespaces in its name. In other words these can be triggered by
calling the scripts from any folder that contains whitespaces.
More info on this specific finding by shellcheck:
https://github.com/koalaman/shellcheck/wiki/SC2046
* [action] Cache QT install files
* Take into account two windows builds
Note: If for any reason the cache is corrupted, the cache key will need to be updated to make it re-build.
