[BUG]: Agent Table links to Network error

[gpascal123]

When clicking on the hyperlink in the cracked column, an error appears.

Should only the cracked entries of the agent be displayed here, not all cracked entries?
→ Check if a corresponding API call exists

Has to be discussed, what should happen if the hyperlink is clicked.

[gluafamichl]

We can't reproduce this error at the moment, it may depend on deletion of agents, which still are referred in hashes table. Problem should be checked be external testers.

[gluafamichl]

There are several problems with the cracked link, maybe we need more issues for that:

• For some agents we see the network error, for some not. Needs to be checked with API changes
• From my understanding, clicking the cracked link in the agent or task table should only display hashes cracked by this agent or task. But we see all hashes from all tasks or agents, cracked and uncracked. See old UI for correct behaviour.
• We always get two API calls to the backend API, the first with limit=9000, the second one with limit=25. We see no reason to do these calls, which lead to unnecessary backend and DB load.

[ObsidianOracle]

Frontend has to be compatible with the api before checking the ticket again