Use edit-distance to fix typos in cabal fields

[crtschin]

Closes #4357.

This adds a pretty simple function for calculating the edit distance between two strings and uses it to score suggestions in completion lists. Some

• I increased the cost of substitutions, otherwise the suggestions would very often lean towards nonsense.
• Kind of hackily injected the Matcher that's used in scoring texts into CompleterData. Couldn't really massage that into the weightedConstantCompleter that's used for licenses.
• This new scoring function doesn't do any filtering, so I had to adjust the cabal codeaction golden test to pick the top action per diagnostic.

[fendor]

LGTM, thank you for taking care of this!

[fendor]

LGTM, thank you very much!

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[fendor]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[crtschin]

I'm not sure I understand why the test is failing. It doesn't look related to my changes. I can reproduce this locally, but the same test also fails on master on my machine.

I tried checking the failing test, but also don't see why it could be flaky though (if flaky tests are a thing in this repository). I might need some pointers.

[fendor]

@crtschin Don't worry about it, most of our tests are unfortunately flaky one way or another :) I restarted the job, should be fine.