Invalid FileDescriptorSet in 0.47

[aaronc]

Summary of Bug

cosmos.reflection.v1 returns an invalid FileDescriptorSet that can't be built by protodesc.NewFiles.

Version

v0.47.0-rc1

Steps to Reproduce

In testing #14696, @julienrbrt ran into these issues

grpcurl v047.simapp.zone:9090 cosmos.auth.v1beta1.Query/Accounts
However, trying to use cosmcli with v047 gives me this:
julien:~/ $ cosmcli --init simapp
Configuring simapp
Unable to load data for simapp in the chain registry. You'll have to specify a gRPC endpoint manually.
Enter a gRPC endpoint that you trust: v047.simapp.zone:9090
Selected: v047.simapp.zone:9090
Error: error building protoregistry.Files: proto: file "gogo.proto" has a name conflict over gogoproto.goproto_enum_prefix
Usage:
[flags]

Examples:
cosmcli --init foochain

Flags:
-h, --help help for this command
--init string initialize a new chain with the specified name

panic: error building protoregistry.Files: proto: file "gogo.proto" has a name conflict over gogoproto.goproto_enum_prefix

goroutine 1 [running]:
main.main()
/home/julien/projects/cosmos/cosmos-sdk/client/v2/cmd/cosmcli/main.go:13 +0x51
Some other times I get some other errors like: Error: error building protoregistry.Files: proto: file "descriptor.proto" has a name conflict over google.protobuf.FileDescriptorSet

This indicates that the cosmos.reflection.v1 service we added in v.047 is returning a FileDescriptorSet with duplicate proto files that can't be turned into a valid instance of https://pkg.go.dev/google.golang.org/protobuf@v1.26.0/reflect/protoregistry#Files. This will cause problems for clients downstream, including but not limited to autocli.

Proposed Solution

1. NewReflectionService should return an error whenever the FileDescriptorSet can't be built into protoregistry.Files with helpful error messages and links to documentation. In particular, @testinginprod suggests to return errors in the following cases:

• two proto files have equal content but are registered with different paths
• two proto files are registered with the same path but have different content

2. Clean up any such issues originating in the SDK that will be passed on to downstream users - in particular the duplication of gogo.proto and maybe descriptor.proto

[aaronc]

@AmauryM here's where tendermint/liquidity is messing up import paths:

• https://github.com/tendermint/liquidity/tree/develop/third_party/proto/cosmos_proto
• https://github.com/tendermint/liquidity/blob/develop/proto/tendermint/liquidity/v1beta1/tx.proto#L5 and the rest of .proto files in that dir