[Feature Request] Investigate if for SPARQL endpoints Service Description provides usefull statistics

## Description

For large public sparql endpoints such as [uniprot](https://sparq.uniprot.org/) statistics gathering takes a long time.
UniProt and other endpoints provide detailed statistics with VoID, which might be useful to avoid sending out a lot of statistics gathering queries.

## Preferred Solution

Gather the maximum of data from a VoID response if it is available.

## Additional Context

Rewriting the discovery queries on the server side to retrieve information from the `/.well-known/void` graph instead.

## Related Issues

## Tasks
- [] implement VoID/service description parser
- [] determine if that contains enough data for aws graph-explorer
- [] document the behavior / trust level of the void data.
---

> [!IMPORTANT]
> If you are interested in working on this issue or have submitted
> a pull request, please leave a comment.

> [!TIP]
> Please use a 👍 reaction to provide a +1/vote.
>
> This helps the community and maintainers prioritize this request.

Start by investigating the existing SPARQL discovery queries and how the server-side query rewriting is organized; no files or tests are named in the issue. Compare available VoID and Service Description responses, then define whether they provide enough data for graph-explorer, implement parsing if appropriate, and document the behavior and trust level.

Written by the indexing model from the issue text.