Absinthe Graphql batching queries

### Is your feature request related to a problem?

Currently all request within a graphql query are done sequentially. This can create latency for the user to receive it's data.

### Describe the solution you'd like

Using a mechanism to execute request concurrently.

### Additional context

https://hexdocs.pm/absinthe/batching.html
https://hexdocs.pm/absinthe/dataloader.html

### Epic

_No response_

Start by reading the linked Absinthe batching and Dataloader documentation, then locate the GraphQL request execution path in this repository. The issue does not name files or tests; done would require an agreed design for concurrent independent requests and evidence that query latency improves without changing results.

Written by the indexing model from the issue text.