octave-kernel: fix broken logo path and modernize meta

[thomasjm]

Description of changes

This kernel is currently broken due to a change in the path to the logo PNG upstream. This PR fixes it and also modernizes the meta field slightly.

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.11 Release Notes (or backporting 23.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.

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-ready-for-review/3032/2474

[SuperSandro2000]

This PR fixes it and also modernizes the meta field slightly.

This is nonsense, it does not matter if meta is using with lib or not and neither is more modern than the other.

[thomasjm]

@SuperSandro2000 so I would have thought, but a previous reviewer felt strongly about it:

#244775 (comment)

[SuperSandro2000]

He is at least partly wrong about it. nil, probably the best lsp right now, can handle with lib properly in some cases already and I only expect it to become better over time. There is currently no tool I know which falls apart when with lib is used and honestly it would probably be pretty weak if it couldn't handle this.

The problems with with only starts to become a problem when you layer multiple with on the same level with similar package sets. So something like with pkgs; with qtPackages; with plasma5Packages; is definitely to be removed.