multi-repl: Support module renaming for ghc-9.12 onwards

[mpickering]

In ghc-9.12 the -rexported-module flag was extended to add support for module renaming.

Therefore now if a module uses a module renaming, then the -reexported-module flag is passed the renaming.

Fixes #10181

Please read Github PR Conventions and then fill in one of these two templates.

---

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
  • Is the change significant? If so, remember to add significance: significant in the changelog file.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.
• Tests have been added. (Ask for help if you don’t know how to write them! Ask for an exemption if tests are too complex for too little coverage!)

---

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

[mpickering]

Fixed the test being run with a GHC version which doesn't support multi-repl at all.

[Mikolaj]

@mpickering: let me take the liberty of setting the review-needed label.

[mpickering]

Two weeks and no reviews, can I merge this patch? I am confident it's correct.

[geekosaur]

We still require reviews. The past two weeks have just been roughly the worst possible time to get me to do reviews, though. 😖

[Mikolaj]

LGTM

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ Bootstrap post job

You can check the last failing draft PR here: #10987.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.