feat: support send and recv msg size for gRPC (backport #170)

[mergify]

This is an automatic backport of pull request #170 done by Mergify.
Cherry-pick of ca48456 has failed:

On branch mergify/bp/v0.45.0x-osmo-v7/pr-170
Your branch is up to date with 'origin/v0.45.0x-osmo-v7'.

You are currently cherry-picking commit ca48456f7.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   contrib/rosetta/node/data.tar.gz
	modified:   server/config/config.go
	modified:   server/config/toml.go
	modified:   server/grpc/server.go
	modified:   testutil/network/util.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   server/start.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[adizere]

should be 10MB

[adizere]

FYI: Multiple IBC relayer operators reported problems with the following symptom:

gRPC call failed with status: status: ResourceExhausted, message: "grpc: received message larger than max (26 vs. 0)"

or

relayer error: gRPC call failed with status: status: ResourceExhausted, message: "grpc: received message larger than max (14 vs. 0)"

Note the 0 value. Is it possible that the default for some of these values here is misconfigured to 0?

The fix they used was to add to app.toml of their Osmosis full node

max-recv-msg-size = "10485760"

max-send-msg-size = "2147483647"

[alexanderbez]

The defaults are defined in server/config/config.go