Allow wdqs_requester() and query_wikidata() to request other instances

[pachevalier]

https://query.wikidata.org/sparql is the main instance which is used to query Wikidata. However, in some context, other instances may be useful. For instance, https://qlever.cs.uni-freiburg.de/wikidata/ is sometimes used to run big queries on a dump of Wikidata. Another instance is https://wikidata.demo.openlinksw.com/sparql.

I think it would be useful to add an instance parameter to wdqs_requester. Do you think it's a good idea ?

[maelle]

@pachevalier maybe you'd like to try out glitter for that? 😁 https://github.com/lvaudor/glitter

cc @lvaudor

[bearloga]

Looks like this will need to happen before March 2025 due to the Wikidata graph split (https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/September_2024_scaling_update)

I'm not going to be able to keep up with any future splits that occur so instead of hardcoding the scholarly endpoint (query-scholarly.wikidata.org/sparql) as one of the options, I'll keep the main one as default and open it up as a parameter for end users to change if they want to – including to non-WDQS instances.