build with docker and improve CUDA compute capability support

[ReenigneArcher]

Description

• Move several Linux builds back to docker. This will resolve dependency issues where the user's environment didn't match our build environment.
• Adds aarch64 packages for deb and rpm packages.
• CUDA compute capability is now determined with logical tests in CMakeLists.txt
  • Fedora 36+ only provides GCC-12, and therefore CUDA 12.x is required. It was found that CUDA Compute Capability 35 is not supported in GCC-12, and further discovered that only CUDA Compute Capability 35 was selected in the previous builds. Now, all supported CUDA Compute Capabilities are selected at build time, based on the installed version of CUDA. I could not find an easy way to install GCC < 12 on Fedora.
• Linux build instructions have been updated to reflect discoveries found during the process of moving back to the Docker images.
• Adds libmfx as required for Bump ffmpeg #769.
• Adds Ubuntu patches to Flatpak build dependencies, replacing Add Ubuntu patches #774.

⚠️ aarch64 builds in the Fedora images are painfully slow. I'm not yet sure why this is so much slower than the Ubuntu images.

Todo:

• get it working
• extract package from docker buildx
• create docker images for various distros and versions
  • Debian Bullseye
  • Fedora 36
  • Fedora 37
  • Ubuntu 20.04
  • Ubuntu 22.04
• update CI
  • remove RPM build from CI
• publish to docker, tag based on image name
• double check workflow
• triple check workflow
• workflow files to .github repo
  • make sure it works for other LizardByte Docker projects and update them if required (Testing in update docker workflow RetroArcher#190 ... small change required when artifacts are not built in Docker image)
• add release step to upload release assets

For Another PR:

• add Arch image (probably a separate PR)
• remove AUR job from CI (probably a separate PR)
• remove arch linux package action repo from LizardByte (less to maintain)

Update: Will not build AppImage with Docker. More context:

• How to build an AppImage using Docker AppImageCommunity/pkg2appimage#150 (comment)
• AppImageCommunity/pkg2appimage@4f8377c
• fuse: device not found, try 'modprobe fuse' first s3fs-fuse/s3fs-fuse#647

Screenshot

Issues Fixed or Closed

• Fixes 0.16 rpm can not install on Fedora 37 due to dependency issue with libcurl #577

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