Update linkcheck dependency

[timobrembeck]

Short description

Finally, our upstream contributions to the linkcheck library have been released! 🎉

Proposed changes

• Update dependencies (including linkcheck version 2.0.0)
• Remove workaround for linkcheck app
• Fix the link test data

Side effects

A lot of other improvements to the link checker, the most important being:

• No crash of the process anymore when long URLs occur
• The findlinks command now deletes outdated links - no need to delete the entire link database anymore
• Broken anchors are now considered valid links instead of broken links (this means we do not need a separate warning category, see Add warning category to broken link checker #1695)
• SSL certificates are now verified

Resolved issues

Fixes: #1695
Fixes: #1818

---

Pull Request Review Guidelines

[codeclimate]

Code Climate has analyzed commit b1f97b8 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 0.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 74.6% (0.1% change).

View more on Code Climate.

[ulliholtgrave]

This looks very nice and seems to solve some issues 🤩

As we are already updating our dependencies I would like to ask you to update our whole dependencies and bump TinyMCE to "^5.10.7". This would also fix the vulnerability of https://github.com/digitalfabrik/integreat-cms/security/dependabot/17.

[timobrembeck]

As we are already updating our dependencies I would like to ask you to update our whole dependencies and bump TinyMCE to "^5.10.7". This would also fix the vulnerability of https://github.com/digitalfabrik/integreat-cms/security/dependabot/17.

Alright, I now updated all dependencies, including the npm dependencies. This required a few changes in the lucide icon replacement, could you check again whether I messed something up? 😇

[JoeyStk]

Thank you a lot! This also worked on my machine. My only thought was that maybe we could add an entry to the changelog. I know that for changes that are mostly relevant to developers we don't add an entry, but since this PR fixes issues that are also relevant for members of the service-team it could be beneficial to add one. What do you think? :)

[timobrembeck]

My only thought was that maybe we could add an entry to the changelog. I know that for changes that are mostly relevant to developers we don't add an entry, but since this PR fixes issues that are also relevant for members of the service-team it could be beneficial to add one. What do you think? :)

Ok, I added one entry for the broken hash anchors, or which changes did you mean?
The other changes are probably more infrastructure-bound, since the issues will not be fixed as soon as the new version is released and installed, but only when we perform the next re-scan of the links...