haskell.{compiler,packages}: Add aliases without minor versions

[maralorn]

Description of changes

We frequently have to bump a lot of references when a minor version of a ghc get’s released. These shorter names lead to less churn for us and downstream users.
By keeping the long version name we still have the option to have multiple versions at the same time and don‘t break any downstreams.

I fear that the change as is will do wrong things to hydra. Would appreciate feedback.

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/)
• 22.11 Release Notes (or backporting 22.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
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[cdepillabout]

We talked about this before and I think we all agreed it would be nice to have these aliases.

Thanks!

Maybe if you're feeling generous you could also add a note about these additional aliases to the release notes (but even if you don't, I feel like no big deal, its not like these aliases would hurt anyone).

[maralorn]

@sternenseemann do you think this is okay to throw at hydra or do we maybe need to add the new aliases to more blocklists to reduce the number of generated jobs?

[maralorn]

I added a changelog entry.

[maralorn]

Oh, I think hydra should be fine since there is an explicit list of packages for which to create test jobs.