chore: Move WebRetriever's new init parameter to last parameter position

[vblagoje]

Why:

The change aims to minimize the potential for breaking existing clients by moving the new WebRetriever init parameters to the last position. This ensures backward compatibility while introducing new customization options.

What:

Modified the init method of WebRetriever to push allowed_domains and link_content_fetcher as the last parameters in the method signature.

How can it be used:

No changes in usage; two new parameters (allowed_domains and link_content_fetcher) have been added as the last init parameters for optional customization.

How did you test it:

No new unit tests were added. The existing tests should cover the basic functionality. In fact, they should by their own nature test this change. I also reran all WebRetriever examples in examples dir.

Notes For Reviewer:

Please ensure that the new parameters are correctly positioned and that this change doesn't introduce any unintended side effects or break existing functionality.

[coveralls]

Pull Request Test Coverage Report for Build 6013272493

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 6 unchanged lines in 1 file lost coverage.
• Overall coverage remained the same at 48.351%

---

Files with Coverage Reduction	New Missed Lines	%
nodes/retriever/web.py	6	92.08%

Totals
Change from base Build 6013155795:	0.0%
Covered Lines:	11496
Relevant Lines:	23776

---

💛 - Coveralls

[vblagoje]

Seems all good @silvanocerza

[silvanocerza]

Perfect, let's go! 🚀