Added cosmos gRPC docs

[crypto-eddy]

• Note that the cosmos-grpc-docs.md file is a tool generated file

[lezzokafka]

Thanks @eddycpc! One quick suggestion before i go ahead:

• I think some of these items can be categorized by different modules on the sidebar?
• Should #google.protobuf.* pointing to somewhere?

[leejw51crypto]

lgtm

[crypto-eddy]

@lezzokafka

The docs in the cosmos-grpc-docs.md file are auto-generated by https://github.com/pseudomuto/protoc-gen-doc.
I don't know if it's worth manually modify the auto-generated file since as the .proto files get updated often, we might always come back to generate again.

I think some of these items can be categorized by different modules on the sidebar?

In this case, we might have to generate these files one by one

Should #google.protobuf.* pointing to somewhere?

This might probably require us to include all third-party definitions, this file might extremely large I think.

[calvinaco]

@lezzokafka

The docs in the cosmos-grpc-docs.md file are auto-generated by https://github.com/pseudomuto/protoc-gen-doc.
I don't know if it's worth manually modify the auto-generated file since as the .proto files get updated often, we might always come back to generate again.

I think some of these items can be categorized by different modules on the sidebar?

In this case, we might have to generate these files one by one

Should #google.protobuf.* pointing to somewhere?

This might probably require us to include all third-party definitions, this file might extremely large I think.

I agree with @eddycpc , I think we can leave the doc this way.

[calvinaco]

On the other hand, I think it is better to crate a simple scripts for generating the docs. That way everyone can generate it in the future.

[calvinaco]

/staging

[lezzokafka]

I see. Sure if it's just for reference 👯

[crypto-eddy]

On the other hand, I think it is better to crate a simple scripts for generating the docs. That way everyone can generate it in the future.

This is a good suggestion, I thought about this too but I realized it would be cool if that automation script can be done in a separate PR to keep this one small and focused on a single task.

That task to add an automated script to download the latest gRPC definitions and generate a new doc file can be a separate task on its own I believe

[lezzokafka]

That task to add an automated script to download the latest gRPC definitions and generate a new doc file can be a separate task on its own I believe

Sure, feel free to start a separated issue for that.

[crypto-eddy]

On the other hand, I think it is better to crate a simple scripts for generating the docs. That way everyone can generate it in the future.

This is a good suggestion, I thought about this too but I realized it would be cool if that automation script can be done in a separate PR to keep this one small and focused on a single task.

That task to add an automated script to download the latest gRPC definitions and generate a new doc file can be a separate task on its own I believe

Related to #33