Remove old mkVersion

[zlonast]

We don't have any testing for such old versions of ghc. Since this code isn't used, I assume it doesn't work, but it's difficult to confirm otherwise.

We just dropped everything below 8.0.0

---

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!)

[zlonast]

Should we drop compilers below 8.6? Or 8.8?

[ffaf1]

This does modify behaviour, does it not?

[zlonast]

@ffaf1 It seems to me that if I can't compile the code with an old compiler, then this doesn't count as a change in behavior.

[ffaf1]

@ffaf1 It seems to me that if I can't compile the code with an old compiler, then this doesn't count as a change in behavior.

Makes sense!

[ffaf1]

This is the same problem, is it not?
Will zSuppoerCpp ever be False?
Or is it different?

[ffaf1]

I would like your comment on this one.
Why did you bump the bound?

[Bodigrim]

Perhaps because base < 4.21 is outdated by now?..

[ffaf1]

And this is related to removing stale mkVersion because…?
I do not see separate commits, so I am sure there is a rationale.