[Subtask] Provide support for Qaku

[weboko]

Description

This issue is to track all relevant problems and requests that are needed to make Qaku more usable.

[vpavlin]

Thanks for creating this!

My main issues are

• the Filter instability
• Store nodes returning

  Store query failed with status code: 300, description: BAD_RESPONSE: archive error: DIRVER_ERROR: error in runStmt: error in 
  dbConnQueryPrepared calling waitQueryToFinish: error in query: ERROR:  out of shared memory
  HINT:  You might need to increase max_locks_per_transaction.
  

  This is obviously problem of nodes with too little RAM, but js-waku should probably disconnect from them after a few failures?
• Concurrent store queries leading to Cannot push value onto an ended pushable

From the perspective of Qaku itself a few things that need some attention:

• UX when a message is published - should the button stay disabled until the message is delivered back by either Filter or Store (or should we also add more frequent Store checks based on message hash?)
• Initial loading - there is a race where Qaku never really loads if waiting for peers take too long

[danisharora099]

@vpavlin is there an update on the state of stability now?

Re Waku:

• Filter is now stable(r)
• cc @Ivansete-status for Store SHM -- is there a permanent resolution for this, or should we cater for this on js-waku level? (perhaps should do it any way assuming the network can be unstable? :D)

[Ivansete-status]

@danisharora099 - I think we may need to look for another approach in some PostgreSQL queries. My bet is that this issue comes due to a temporary table that a message-hash query creates. Therefore, I see a reason for changing this approach.
Other than that, the only solution is to make sure the database host configures a bigger shm_size (I use to recommend 1GB.)

[weboko]

I think we still want to make Quaku great again.
Maybe we can think of some other solution here to temporarily substitute Store, @vpavlin? That way we can get some feedback on anything but store from Town hall and such.

Also, can we integrate some telemetry into Quaku so that we can technically track behavior of js-waku?

[fryorcraken]

Limit time range queries to 24 hrs max, like in Status. I'd expect that to be actually provided by the messaging API.
You can still do more than one query. but avoid unbounded queries.