feat: Implement E2E Reliability PoC in an example application

[shash256]

Problem

Lack of an end-to-end reliability mechanism in Status chat, which can lead to message loss and inconsistent message ordering in large group chats or under poor network condition

Suggested solution

Implement a Proof of Concept (PoC) for an end-to-end reliability mechanism based on lamport timestamp, ACKs and bloom filters, as an enhancement to the chat2 example application. This solution, based on @jm-clius's proposal, will use bloom filters to track message acknowledgments and ensure reliable message delivery without significant overhead. Please note that this POC is a step towards integration with status-go and this work is NOT intended to be merged to go-waku at this point.

Alternatives considered

• Research Alternatives:
  Vector clocks: While effective for smaller groups, they don't scale well for large communities.
  Merkle trees: Provide strong consistency but require more complex synchronization processes.
• Implementation Alternatives:
  Standalone repo: Would be complex a lot of Waku related stuff needs to be imported. chat2_reliability, as an enhancement to chat2 is the fastest and straightforward path to test this idea

Acceptance criteria

• Implement or re-use any existing bloom filter package
• Define a new payload and create chat2_reliability to work with the new payload
• Test and validate this approach, document any learnings prior to status-go integration