@adklempner to add description

also we need to add E2E interop tests for this usage of Store

related to #2330

Issue Summary: Store v3 Message Hash Query Fix

Problem

The Waku Store v3 message hash query test was failing in js-waku CI. Initial investigation suggested it was an nwaku issue, but further analysis revealed the problem was in the js-waku implementation.

Root Cause

1. Missing pubsubTopic in test: The test was not specifying the pubsubTopic when querying by message hash
2. Incorrect RPC validation: The js-waku RPC validation was incorrectly rejecting hash queries that included pubsubTopic
3. Wrong assumption: The js-waku implementation assumed hash queries should not include pubsubTopic, but according to Waku protocol, pubsubTopic should always be specified

Solution

The following changes were made to fix the issue:

1. Updated the test (packages/tests/tests/store/message_hash.spec.ts):

   // Added pubsubTopic to the query options
   for await (const page of waku.store.queryGenerator([TestDecoder], {
     messageHashes,
     pubsubTopic: TestDecoder.pubsubTopic
   })) {

2. Fixed RPC validation (packages/core/src/lib/store/rpc.ts):

   // Changed validation to allow pubsubTopic in hash queries
   if (isHashQuery) {
     // Message hash lookup queries cannot include content topics or time filters
     // but pubsubTopic is allowed/required
     if (hasContentTopics || hasTimeFilter) {
       throw new Error(
         "Message hash lookup queries cannot include content filter criteria (contentTopics, timeStart, or timeEnd)"
       );
     }
   }

3. Updated store logic (packages/sdk/src/store/store.ts):

   // Use pubsubTopic from options if provided, otherwise from first decoder
   pubsubTopic = options.pubsubTopic || decoders[0]?.pubsubTopic || "";

Test Result

After applying these fixes, the test now passes successfully:

✔ can query messages by message hash (201ms)

The nwaku logs confirm that queries now include the proper pubsubTopic and messages are successfully retrieved.

Key Takeaway

The issue was not in nwaku but in js-waku's implementation and test. The Waku protocol requires pubsubTopic to be specified for all store queries, including hash queries. The js-waku implementation incorrectly assumed hash queries should exclude pubsubTopic.

Related PR

This investigation was done while analyzing failing CI tests in js-waku PR #2250.