As an editor of Wikidata, I want to have WikibaseQualityConstraint check data imported to WDQS so that I can build higher level workflows to improve the quality of Wikidata.

As part of the WDQS Streaming Updater work (T244590), import of Constraint Checks will stop being imported into WDQS. The current way constraint checks were imported was problematic and failed to import a large amount of the data (citation needed). Instead of reimplementing a problematic solution, we want to have a robust one from the start. The exact strategy still needs to be defined.

A few notes:

• a robust implementation will need Store WikibaseQualityConstraint check data in persistent storage instead of in the cache (T204024)
• Wikibase will probably need to expose a stream of constraint check changes
• constraint checks will need to be identifiable (so that they can be removed from WDQS)
• the WDQS Flink based Streaming Updater will need to be modified to support constraint checks

AC:

• Constraint check data is available in a SPARQL endpoint and available to be queried with WDQS