chore(frontend): find a better solution for refetching after a core tx is executed #61
Description
In side panel, when executing a transaction there is a short delay before database is updated because of the flow:
frontend ---tx---> chain --------> indexer ----ws----> backend ------> db
If the frontend tanstack mutation triggers a refetch immediately after successfully executing a transaction, the database is not yet updated and neither is data on front. Right now the solution is to set a timeout of 1500ms before refetching but obviously this is not ideal since the update of the db is has unpredictable timing. Instead mutation should either poll the database until it gets a new value (not ideal as well because with many users can change a market and some other change may be fetched first) or use websocket.
Hopefully, when #42 is implemented this problem can by solved with it.