fix: add HCS message query integration test

[AlexanderShenshin]

Description:
Adds HCS message query part for integration tests, currently can be used as reproduction sample for: #75

Related issue(s): #75

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[AlexanderShenshin]

Temporary change o fork, will not be needed once hiero-ledger/hiero-solo-action#37 is merged.

[nadineloepfe]

let's in that case wait until your solo-actions PR is merged, will try to chase

[nadineloepfe]

hey @AlexanderShenshin: could we change this to the newest solo version so we can merge it in? Thanks

[exploreriii]

@AlexanderShenshin. I have just merged solo action v0.8, please refactor for the final review when you can. Thank you

[nadineloepfe]

@AlexanderShenshin: any updates on this please?

[AlexanderShenshin]

Hi @nadineloepfe, @exploreriii !
Sorry for late response, I was on vacation.

I removed usage of forked Hiero Solo action + created a separate integration test for HCS Message Query.
However, it looks like the issue still persists - the test passes against testnet (checked locally), but not against solo network that we use in CI.

[nadineloepfe]

ok so seems to be a problem with the solo mirror node. it probably doesn't have enough time to fetch the topics. can we try the following?

• increasing MESSAGE_WAITING_TIMEOUT to like 60s
• increasing the sleep time in test_integration_topic_message_query_returns_all_messages before querying (await asyncio.sleep(60) or smth like that)

if that doesn;t fix it then we need to check if the connection to localhost:5600 is established, as looking through the logs the the network.py seems to be still correctly configured @AlexanderShenshin

[nadineloepfe]

Hi @AlexanderShenshin : any new regarding this PR? thanks

[AlexanderShenshin]

Hi @nadineloepfe!

I've tried to increase timeouts/wait time and using a recently updated version of Hiero Solo - doesn't fix the issue. Query returns some messages, but not all of them and it's unstable (with 60 seconds timeout it returned 2 out of 3 and with 120 seconds - 1 out of 3).

All other tests are working and, based on my initial observations in DID SDK, only HCS messages resolution is affected.

So it seems that there is a specific issue with querying messages from Hiero Solo mirror node.
I'm not sure if it's caused by SDK behavior or Hiero Solo itself, or if this can be fixed with some simple configuration update/workaround.

Sorry, I don't have enough time to debug this further at the moment (and this is a bit out of scope for me, to be honest).
This PR was initially created as reproduction example for: #75