electron_32-bin: mark as insecure because it's EOL, electron-source.electron_32: remove as it's EOL

[emilylange]

Previously:

• electron_31-bin: mark as insecure because it's EOL, electron-source.electron_31: remove as it's EOL #370758
• electron_30-bin: mark as insecure because it's EOL, electron-source.electron_30: remove as it's EOL #350549
• electron_29-bin: mark as insecure because it's EOL, electron-source.electron_29: remove as it's EOL #335850

electron_32 will be EOL in two weeks (2025-03-04).

https://www.electronjs.org/docs/latest/tutorial/electron-timelines (permalink)

This PR removes the source build on Linux for electron 32 and marks the binary variants for Darwin and Linux as insecure.
electron_32 will still be available for an undetermined while. Linux will simply use the binary package instead of the source build, just like Darwin.

After this PR has been merged, users will be able opt-into the EOL version of electron as outlined by this eval error message:

# nix-instantiate -A electron_32
error:
       … in the condition of the assert statement
         at ./lib/customisation.nix:419:9:
          418|       drvPath =
          419|         assert condition;
             |         ^
          420|         drv.drvPath;

       … while evaluating the attribute 'handled'
         at ./pkgs/stdenv/generic/check-meta.nix:507:7:
          506|       # or, alternatively, just output a warning message.
          507|       handled =
             |       ^
          508|         (

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: Package ‘electron-32.3.1’ in ./pkgs/development/tools/electron/binary/generic.nix:37 is marked as insecure, refusing to evaluate.


       Known issues:
        - Electron version 32.3.1 is EOL

       You can install it anyway by allowing this package, using the
       following methods:

       a) To temporarily allow all insecure packages, you can use an environment
          variable for a single invocation of the nix tools:

            $ export NIXPKGS_ALLOW_INSECURE=1

          Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,
                then pass `--impure` in order to allow use of environment variables.

       b) for `nixos-rebuild` you can add ‘electron-32.3.1’ to
          `nixpkgs.config.permittedInsecurePackages` in the configuration.nix,
          like so:

            {
              nixpkgs.config.permittedInsecurePackages = [
                "electron-32.3.1"
              ];
            }

       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
          ‘electron-32.3.1’ to `permittedInsecurePackages` in
          ~/.config/nixpkgs/config.nix, like so:

            {
              permittedInsecurePackages = [
                "electron-32.3.1"
              ];
            }

The following packages are affected by this. Note that those package will continue to work, but users will be presented with the eval error above and have to opt-in.
If you are pinged as one of the maintainers of such package, you can do one of the following:

1. Check if upstream supports a newer electron version and open a PR in nixpkgs to use that instead OR
2. Try using a newer electron version than upstream suggests and if that turns out to be stable, open a PR in nixpkgs to use that instead OR
3. Do nothing in nixpkgs, and maybe make upstream aware that their electron version is EOL.

• heroic (@aidalgol) heroic-unwrapped: electron 32 -> electron 33 #383732
• legcord (@wrmilling @water-sucks) legcord: 1.0.8 -> 1.1.0, electron_32 -> electron_34 #383696
• lx-music-desktop (@oosquare)
• morgen (@justanotherariel)
• teams-for-linux (@muscaln @qjoly @chvp @khaneliman) teams-for-linux: electron_32 -> electron_33 #383663
• zulip (@andersk)

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/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 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.

[teutat3s]

Thank you!