Add subscriptions when something has to be written to the blockchain

[zacck-zz]

Is your feature request related to a problem? Please describe.
In a number of situtations our application has to write information the the blockchain then that has to be transferred to the backend and finally the front end can show it.

Sometimes it's misleading to show a user stale information such as when an action is being created, redirecting back to the objective too soon would make i it look like the action creation failed

Describe the solution you'd like
We need to list the updates that go through the blockchain and make subscriptions for them so that we can have the frontend wait for their creation before it can show a user some results

Describe alternatives you've considered
None

Additional context
Data needs to go to the blockchain then it can be broadcasted to the backend, this usually takes a few seconds and we should initiate waits for this

@lucca65 I think a while ago you listed these scenarios in slack but I can't seem to find the message in question

[lucca65]

Finally some advancements on this. Today @NeoVier discovered that we have an responded status on our GraphQL subscriptions, this means that we can let the frontend knows about information that was already processed (I always thought that we could only get info if we are listening when it happens received).

This means that its possible to create a implementation that takes a transaction_id instead of a symbol or something similar, creating a generic subscription that can be triggered on any context.

I'm moving this to the backend to be addressed