Update boostraps on master as per B.2.0 of Release plan

[Mikolaj]

Fixes #12233. To be frank, I'm not sure how the resulting dep bumps help people using or abusing the boostrap files (the intended purpose of the files is porting to new architectures, but some distros apparently build from that, too), but if this is not welcome, let's hope they tell us. In principle, this should work as in previous releases and nobody complained then.

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

[ulysses4ever]

So you're changing a released version (3.18.1.0) to an unreleased one (3.19.0.0)? Is there a justification? Sorry if it's a silly question, I'm not very competent with bootstrapping, but it just looks very suspicious.

[Mikolaj]

Let me try to guess: dudes don't have a cabal-install executable, because that's why you need to bootstrap, so they can't use Hackage via cabal, so they instead checkout the cabal repo, where the cabal version happens to be 3.19.0.0. Most of the deps they get from GHC, and if we depend on anything else, they have to manually download from Hackage anyway, but at least the cabal packages they don't have to.

[ulysses4ever]

To me this doesn’t explain why it used to be a released version and now it suddenly switches to an unreleased. I agree that unreleased looks more plausible though