fix: linkchecker include filter port mismatch (#2242)

* initial commit; fixed anchor links on internal docs pages

* add back in absolute paths for links in code comments

* fix: update linkchecker include filter to match server port 1314

PR #1629 changed the Hugo server to port 1314 but forgot to update
the --include filter, which still matched port 1313. This caused all
links to be excluded, making the checker a no-op (0 checked, 82277 excluded).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Fix url rewrite regex so images are not impacted

* Fix links from non-documentation pages

* Fix broken links

* more broken links

* more broken links

* broken link

* Add srcset width descriptor to .lycheeignore

* Ignore URLs that contain a % character

* Anchor regex so it matches the entire URL

---------

Co-authored-by: kanungle <neil.kanungo@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>

qdrant-landing/content/documentation/tutorials-search-engineering/static-embeddings.md

@@ -135,7 +135,7 @@ ranking quality of search results, with higher scores indicating better performa
 Binary Quantization definitely speeds up the retrieval, and make it cheaper, but also seems not to affect the quality of 
 the retrieval much in some cases. **However, that's something you should carefully verify on your own data**. If you are 
 a Qdrant user, then you can just enable quantization on an existing collection and [measure the impact on the retrieval 
-quality](/documentation/beginner-tutorials/retrieval-quality/).
+quality](/documentation/tutorials-search-engineering/retrieval-quality/).
 
 All the tests we did were performed using [`beir-qdrant`](https://github.com/kacperlukawski/beir-qdrant), and might be
 reproduced by running [the script available on the project