feat(manager): add Cabal/Haskell manager using Hackage/PVP

[ysangkok]

Changes

The Haskell programming language has a package manager called cabal-install, commonly referred to as 'Cabal'. It's package definition files have the extension .cabal.

This PR contains code to extract build-depends fields from .cabal files.

The build-depends field syntax is documented here.

This was tested on the repo https://github.com/ysangkok/haskell-tz (as you can see in the pull requests tab)

Context

For a discussion on this particular feature, see discussion at

• Manager for Haskell Cabal files #31493

Note that this doesn't contain support for package.yaml files which are used
with hpack. package.yaml files are used to generate the cabal files.
So .cabal file support could be considered more general,
since it covers all packages uploaded to Hackage.

However, .cabal files do use a custom syntax which requires a bit of work to parse.
That is the bulk of this PR.

This PR also doesn't contain code to bump e.g. git commit references in
stack.yaml which is mentioned in issue #8187.
This is already implemented in projects like stack-lint-extra-deps,
so I consider it less pressing.

Even though these are largely orthogonal features, they can reuse the
Hackage/PVP code previously added.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[zharinov]

Generally looks good to me, but please rewrite regex

[ysangkok]

@zharinov I have replaced the regex with validation that rejects more invalid package names.

[zharinov]

Could you provide couple repos for testing? For example, fork of some existing one that have many deps, with Renovate configured for it

[ysangkok]

@zharinov Yes, this is the configuration file that I use for testing, named default.json5:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "persistRepoData": true,
  "onboarding": false,
  "enabledManagers": ["haskell-cabal"],
  "packageRules":
    [{ "matchDatasources": ["hackage"]
     , "rangeStrategy": "widen"
    }],
  "platform": "github", // Could also be 'local', but then no PRs are made
  //"dryRun": "full",
  "token": "<paste your github token here>",
  "repositories": [{ repository: 'ysangkok/diagrams-builder' }, { repository: 'ysangkok/haskell-tz'} ],
}

I compile renovate using npm run compile:ts and then execute, in a sibling directory:

RENOVATE_REQUIRE_CONFIG=ignored RENOVATE_CONFIG_FILE=$PWD/default.json5 LOG_LEVEL=debug node ../renovate/dist/renovate.js

I just ran this, and it made PRs:

• https://github.com/ysangkok/diagrams-builder/pulls
• https://github.com/ysangkok/haskell-tz/pulls

[ysangkok]

Sorry to have invalidated the review, but this should now be ready for review again. Per the Slack discussion in #general, I have improved the handling of rangeStrategy. rangeStrategy is converted from auto before it reaches versioning, so it doesn't make sense for versioning to handle only auto. I have corrected this mistake in PVP, and I have made the new manager default to widen, which is the only strategy that PVP supports right now.

[ysangkok]

@secustor You requested in #31434 that I split up the work in at least three PRs. I have done this, and this constitutes the third PR in the series. I am planning further work in separate PRs though, like e.g. adding support for rangeStrategy=pin in the PVP versioning module. But that will be in an upcoming PR, because it is somewhat orthogonal to this PR.

[secustor]

Please add a reference to the real repo you have used to test this manager.

[secustor]

else LGTM

[ysangkok]

@secustor Thanks for all your comments, I am not sure how to further advance this. Not sure if Rhys is waiting for the green check mark?

[secustor]

I had to do a small change, but else LGTM.

Thanks for the patience and contribution!

[renovate-release]

🎉 This PR is included in version 39.107.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 39.107.0

Your semantic-release bot 📦🚀

[wolfgangwalther]

@ysangkok I have an example where the manager breaks some of the surrounding comments:

https://github.com/PostgREST/postgrest/pull/3861/files

It also adds a trailing comma, which is invalid syntax.

[ysangkok]

@wolfgangwalther Thank you for the bug report regarding the comment and the trailing comma, I'll look into that. I'll add it to my issue tracking in the discussion page.