Bump Cabal and Cabal-syntax to allow 3.12

[ffaf1]

I have tested the change by building all against Cabal and Cabal-syntax 3.12.

[ffaf1]

I have bumped anything that was preventing cabal build all && cabal test all to work.
This is slightly more than what strictly needed to get Cabal 3.12 released but I think those bumps are reasonable and will be due anyway.

[Mikolaj]

How about bumping to < 3.14 so that the new dev cabal on master can build without allow-newer?

[andreasabel]

Does this PR make sense already when Cabal-3.12 isn't available yet and so CI cannot pick it up?

P.S.: Unfortunately, the workflows here do not contain an invocation of cabal plan so one cannot even see which version of which package was picked up. (Apologies, looked at the wrong workflow.)

https://github.com/haskell/hackage-security/actions/runs/8332470663/job/22801675832?pr=309#step:15:894

Cabal-syntax-3.10.2.0

[Mikolaj]

Unfortunately we have the chicken and egg problem. In general, cabal can't be made available until hackage-security with permissive bounds is on Hackage, because cabal depends on hackage-security.

[ffaf1]

Yep. See #291 (date: February 2023) too, where Cabal-syntax was bumped to < 3.12 before Cabal syntax 3.10.* was out (March 2023).

This Ouroboros is caused by bootstrap.py and I wonder if there is a way to unbundle it from Cabal release (alternatively: bundle whatever is needed from hackage-security into cabal)

[Mikolaj]

LGTM

[andreasabel]

@Mikolaj @ffaf1 hackage-security 0.6.2.5 has been released. Do you need a release of the hackage-repo-tool as well?

[ffaf1]

It should not be needed, thanks!