Lychee lints CI check failing

[jancionear]

The Lychee Lints CI check is currently failing on all PRs.
For example: https://github.com/near/nearcore/actions/runs/7989919938/job/21817515763?pr=10613

The error message is:

## Errors per input

### Errors in CONTRIBUTING.md

* [403] [https://stackoverflow.com/questions/63341296/github-pull-request-allow-edits-by-maintainers](https://stackoverflow.com/questions/63341296/github-pull-request-allow-edits-by-maintainers) | Failed: Network error: Forbidden
* [403] [https://stackoverflow.com/questions/40893008/how-to-resume-review-process-after-updating-pull-request-at-github](https://stackoverflow.com/questions/40893008/how-to-resume-review-process-after-updating-pull-request-at-github) | Failed: Network error: Forbidden

### Errors in docs/practices/workflows/otel_traces.md

* [404] [https://github.com/PagodaPlatform/tf-near-node/blob/main/doc/otlp.md](https://github.com/PagodaPlatform/tf-near-node/blob/main/doc/otlp.md) | Failed: Network error: Not Found

### Errors in .github/ISSUE_TEMPLATE/bug_report.md

* [403] [https://stackoverflow.com/search?q=nearprotocol](https://stackoverflow.com/search?q=nearprotocol) | Failed: Network error: Forbidden

Error: Process completed with exit code 2.

I can reach those links, maybe the checker is rejected by some kind of bot protection? o-O

It's annoying that the CI is always red, even when the PR is correct. It would be nice to disable this check or fix it.

[jancionear]

Fixed in #10644