Some repositories (namely 24.04) do not have the cuda-archive-keyring.gpg file. All relevant repositories have a .pub file, however.

Added matrixMulDrv, vectorAddDrv, deviceQueryDrv, simpleTextureDrv

This hardcodes the current gpg key and checks its fingerprint.

NOTE: It seems like x86_64 is the only architecture supported
everywhere. Nvidia seems to support arm64 in *some* cases, but not a
lot. Should we only support x86_64, then?

This commit changes the gpu-setup script behaviour to build the cuda-samples
and gpu-burn projects inside the `build/bin` directory, then copy them
out into the `bin/` and (the necessary data files) into `data/`. For the
cuda-samples executables to work, they need access to the data files,
but they do not take the path to the data dir as an argument; to
circumvent this limitation, I have made wrapper scripts that copy the
necessary file into the temporary working directory that checkbox
creates.

Because of the change in build behaviour, the `gpu-setup` script now runs
mostly as a regular user (to avoid permission issues when cleaning
directories/builds). The expected operation now is to run `./manage.py build`
instead of running the `gpu-setup.sh` script itself. This is more inline
with what is done with the other providers.

For now, we are limiting the gpgpu tests to x86_64 since nvidia only
supports x86_64 consistently across distributions/releases.

This allows the packaging to complete. The gpgpu provider still fails
due to some issues with setting up the repository, but it does not
prevent the packaging to complete. We may need to look
into vendorizing some of the dependencies...

These paths are now resolved to absolute paths to the gpgpu provider's
subdirectories. I also made sure to clean up left-over data files in the
wrapper scripts.

This reverts commit a7def84.

We will revisit properly packaging the gpgpu provider at a later time.