ICS31 Cross-Chain Queries integration tests

[ljoss17]

Summary

The ICS31 implemented in #2915 is currently only tested manually with https://github.com/informalsystems/hermes/wiki/Testing-examples#ics31-cross-chain-queries.

There might also be an compatibility issue due to proto definitions. The suspicion comes from the fact that Stride and Persistence use different proto files, https://github.com/Stride-Labs/stride/blob/main/proto/stride/interchainquery/v1/messages.proto and https://github.com/persistenceOne/persistence-sdk/blob/master/proto/persistence/interchainquery/v1beta1/messages.proto.
The integration tests should be able to easily confirm or discard this suspicion.

Problem Definition

In order to test ICS31 with Stride, an admin account is required: https://github.com/Stride-Labs/stride/blob/main/utils/admins.go
So the two solutions to my knowledge are:

1. Adding the necessary Admin account and recompile Stride binary
2. Using Stride's dockernet (which is the solution used in the Wiki)

In order to have some running integration tests in Hermes, a solution which allows to trigger Cross-Chain Queries without modifying Stride's binary or using the dockernet is required.

Proposal

Adding integration tests for ICS31

Acceptance Criteria

• Successful integration tests for ICS31

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned