Build process error and warning for 3.11.0rc1

[pljones]

Describe the bug

When editing the 3.11.0rc1 release, I noticed the following error:

Probably something in the deployment scripts.

There's also a warning relating to macOs in the output:

but may not be related.

To Reproduce

Cut a release candidate.

Expected behavior

No errors

Version of Jamulus

3.11.0rc1 release build.

[ann0see]

I don't think they are related. I believe there's something wrong in two places.

1. Deployment upload
2. macOS caching

[ann0see]

For 1, the cleanest way would be to call gh release upload in the respective scripts instead of the hacky cross platform method we use currently:

jamulus/.github/workflows/autobuild.yml

Lines 434 to 436 in 97388ab

	gh release upload "${{ needs.create_release.outputs.tag_name }}" "deploy/${{ steps.get-artifacts.outputs.artifact_1 }}" "deploy/${{ steps.get-artifacts.outputs.artifact_2 }}" --clobber
	||
	gh release upload "${{ needs.create_release.outputs.tag_name }}" "deploy/${{ steps.get-artifacts.outputs.artifact_1 }}" --clobber

The issue is Windows:
cli/cli#5099

Otherwise, we could just upload every file from the deploy directory with a wildcard.

For 2, further investigation is needed.

[ann0see]

I think for now we'll just split the release upload into two artifacts again.

https://github.com/ann0see/jamulus/releases/tag/r0_3_10_0

[ann0see]

Concerning 2, it seems to be comparable to actions/setup-node#362

Maybe we need to use a non standard location to put Qt to, or just delete the cache.

[pljones]

OK, as it doesn't appear to have a discernable negative effect, I'm bumping the problem to after the release.