ci(codeql): fix codeql builds

[ReenigneArcher]

Description

• Pin macOS code-ql runner to macOS-13 (x86_64) until macos-latest cannot install homebrew packages after using this action github/codeql-action#2266 is fixed
• Fix ubuntu code-ql build (again) by freeing up more space in root reservve for cuda...

This change requires an update to our .github repo, per LizardByte/.github#330

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 7.04%. Comparing base (ff54ab2) to head (f981b85).

Additional details and impacted files

@@           Coverage Diff            @@
##           nightly   #2475    +/-   ##
========================================
  Coverage     7.04%   7.04%            
========================================
  Files           87      87            
  Lines        17697   17697            
  Branches      8405    8405            
========================================
  Hits          1246    1246            
+ Misses       13874   13712   -162     
- Partials      2577    2739   +162     

Flag	Coverage Δ
Linux	5.35% <ø> (ø)
Windows	2.56% <ø> (ø)
macOS-12	8.07% <ø> (-0.02%)	⬇️
macOS-13	7.98% <ø> (ø)
macOS-14	8.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 24 files with indirect coverage changes

[ReenigneArcher]

macOS issue: github/codeql-action#2266

Not sure about Ubuntu issue for now.

[Hazer]

uname can fail, the best way currently is to do:

Suggested change

	#if [[ "$(uname -m)" == "arm64" ]]; then
	#if [[ $(sysctl -n machdep.cpu.brand_string) =~ "Apple" ]]; then

This may solve it

[ReenigneArcher]

I'll keep that in mind, if I could even get arch -arm64 to work. Currently it doesn't even if I hard code it. https://github.com/LizardByte/Sunshine/actions/runs/9055643443/job/24877061140?pr=2475#step:6:48

Which is odd, because that's the suggestion that the original error gives. https://github.com/LizardByte/Sunshine/actions/runs/9054788502/job/24875053065#step:6:56

I also don't understand how the brew install only fails if it's after the code ql init step: github/codeql-action#2266

[Hazer]

oh, thats odd.

arm64e... I guess, ARMv8.3+, maybe they are using an old version of Clang, or LLVM that don't support ARMv8.3+ and they are replacing the version available to the environment?

Interesting links:
https://developer.apple.com/documentation/security/preparing_your_app_to_work_with_pointer_authentication

https://lists.llvm.org/pipermail/llvm-dev/2019-October/136091.html

https://github.com/lelegard/arm-cpusysregs/blob/main/docs/arm64e-on-macos.md