Update cabal-install to allow time 1.14

[geekosaur]

Note that #9848 covers Cabal and Cabal-syntax already.
For sanity's sake, #9848 should probably be committed first.

Template Β: This PR does not modify cabal behaviour (documentation, tests, refactoring, 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). (n/a)

[geekosaur]

As noted in #9848, this needs to be validated locally by reviewers because time is a bootlib. I found I needed an allow-newer as well, because one of our (test?) dependencies didn't have its bounds adjusted yet.

[Mikolaj]

I think @ulysses4ever prototyped a tool to permit precisely such a usage of our own CI, but I can't find docs for it.

[ulysses4ever]

They're at the bottom of CONTRIBUTING.md, I think

[Mikolaj]

Oh, great, thank you. I only searched in READMEs and the Wiki. I've updated the placeholder with the link at the bottom of https://github.com/haskell/cabal/wiki/Cabal-Packages-Hackage-Revision-Policy.

[Mikolaj]

Looks good and Artem reports:

started CI run of the Validate workflow with time==1.14: https://github.com/haskell/cabal/actions/runs/8650585264
will see how it goes
Validate · haskell/cabal@8e971f5 - GitHub
Official upstream development repository for Cabal and cabal-install - Validate · 8e971f5
... it failed for an unfortunate reason: validate uses various ghc and some come with base older than the lower bound on base that time-1.14 has. This is clearly a shortcoming of this approach for testing version bumps :-( I'll think if there's a way around it. But in the meantime you may want to just trust the PR author that they tested it locally on one GHCV at least...
actually, the static exe job succeeded with time-1.14! https://github.com/haskell/cabal/actions/runs/8650585264/job/23719429299

[Mikolaj]

@ffaf1: we have two compilation tests with the bound forced, so I think it's fine for you to approve and set the merge label without repeating the tests.

[Mikolaj]

I've we set the delay_passed label by hand. It's been untouched for 4 days and will now take some more time for CI to pass after rebase anyway.

[ffaf1]

@mergify backport 3.12

[mergify]

backport 3.12

✅ Backports have been created

• #9907 Update cabal-install to allow time 1.14 (backport #9851) has been created for branch 3.12