VSCode, VSCodium 1.78.2 + cleanups

[K900]

Description of changes

https://github.com/microsoft/vscode/releases

Note 1.78.1 is a security patch.

Closes #232296

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• 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/)
• 23.05 Release Notes (or backporting 22.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.

[K900]

Result of nixpkgs-review pr 232280 run on x86_64-linux 1

5 packages built:

• vscode
• vscode-fhs
• vscode-with-extensions
• vscodium
• vscodium-fhs

[gilice]

Why drop armhf?
If you have an amend to the commit message would be appreciated.
It is unclear from the release notes, but maybe it was discontinued upstream?

[K900]

It was in fact discontinued upstream. VSCodium/vscodium@7afbfe0

[gilice]

thanks!

[bobby285271]

Why drop armhf?

The build fails. I imagine the story is similar to VSCodium/vscodium#1072 that upstream has no time to investigate and can be re-enabled once "someone knows how to fix" 🙃 Personally fine for me not to wait for it

(The wayland aarch64-linux test timeout is an existing one)