Bug: newModuleQuerySafeAllowList panics

[julienrbrt]

When using IBC >= 8.2.0 with rollkit, the keeper will panic because of some proto definition not found. It looks like ignite/cli#4318 hasn't entirely resolved the issue.

ref: ignite/cli#4318 (comment)
ref: #6436 (comment)

[damiannolan]

I think this is popping up with rollkit apps using ignite because of the dependency on go-libp2p.
Rollkit app imports rollkit (rather than cometbft) and it depends on go-libp2p - which where the mentioned proto files in the stacktraces seem to be coming from:

• https://github.com/libp2p/go-libp2p/blob/master/core/crypto/pb/crypto.proto
• https://github.com/libp2p/go-libp2p/blob/master/core/sec/insecure/pb/plaintext.proto

I don't have deep understanding of how exactly gogoproto handles the whole proto registry file descriptors via MergedGlobalFileDescriptors etc, and how it populates that registry.
From my understanding, go package loader includes go-libp2p/core/crypto/pb/crypto.pb.go and thus file descriptor is available to be gathered by gogoproto MergedGlobalFileDescriptors

Trying to understand where there is a dependency on these files and/or if not, then why are are we seeing panics when AllowUnresolvable is true. I have not yet stepped through this entire trace with debugger to isolate the exact panic - looks like here https://github.com/protocolbuffers/protobuf-go/blob/v1.34.2/reflect/protodesc/desc_resolve.go#L47
https://github.com/protocolbuffers/protobuf-go/blob/v1.34.2/reflect/protodesc/desc_resolve.go#L201

[damiannolan]

related CosmWasm/wasmd#1785

[damiannolan]

We should test this with rollkit using #7278 which is a branch against v8.5.x rather than the PR targetting main, which would contain a lot more diffs