cuda-modules: rewrite setup hooks

[ConnorBaker]

Important

To-do:

• Merge cuda-modules: apply lessons learned from cross-compilation attempts #301416
• Rebase on changes introduced by cuda-modules: apply lessons learned from cross-compilation attempts #301416

Description of changes

• Moved to a directory structure for setup hooks
• More consistent naming convention for our setup hooks (adding aliases when appropriate)
• Added a logging utility for setup hooks
• Rewrote markForCudatoolkitRoot and setupCuda to make use of new logging utility and do general cleanup

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[ConnorBaker]

@SomeoneSerge of some interest -- we're not in the global scope in the body of these setup hooks, I believe. I was running into errors when trying to use the associative arrays cudaHostPathsSeen and cudaOutputToPath in extendcudaHostPathsSeen inside setup-coda.sh. I've kept the -g flag; in the case you're in the global scope, it is a no-op so at the worst it doesn't hurt anything.

[SomeoneSerge]

I remember a discussion about this, and I agree there's little point in having the suffix, and it's ok not to have it... I don't know why bother renaming old stuff, but no strong opinions here on my part