Change broken link checker to lychee

[tuminoid]

User Story

We have GH workflow lint-docs.yml which basically runs a dead link check on the markdown files. Maintainer of that action suggest moving to his new https://github.com/UmbrellaDocs/linkspector as it is using headless chrome to inspect the links. This would be helpful in reducing false positives, as for example GH is responding 404 to simple bots trying to read its website. This leads to false positive issues being created.

NOTE: we've adapted website repo linkchecker to lychee, so that should be used instead of linkspector.

This same workflow is trying to be added to metal3-docs where we have many more links and it is riddled with false positives.

Detailed Description

• Broken link checker is migrated to the lychee.
• Issues related to broken links in CAPM3 and metal3-docs rechecked for validity, new ones to be opened and false positives closed.

/kind feature

[tuminoid]

/triage accepted
/assign

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[tuminoid]

/remove-lifecycle stale

[tuminoid]

/assign @peppi-lotta
/unassign @tuminoid

Updated ticket to say lychee, as we chose that instead of linkspector.

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

/remove-lifecycle stale
@peppi-lotta are you working on this?

[peppi-lotta]

I have not been working on this but it is in my TODO list.