R4R: Indicate build flags in version

[jleni]

This PR adds build tags to the version command:

cosmos-sdk: 0.31.1-10-gfe548c08
git commit: fe548c0
vendor hash: 1aec7edfad9888a967b3e9063e42f66b28f447e6
build tags: netgo ledger
go version go1.11.5 linux/amd64

This is useful to understand which features were enabled when building the binary.
The issue is related to #3528

• Targeted PR against correct branch (see CONTRIBUTING.md)

• Linked to github-issue with discussion and accepted design OR link to spec that describes this work.

• Updated relevant documentation (docs/)

• Added entries in PENDING.md with issue #

• rereviewed Files changed in the github PR explorer

• Wrote tests

---

For Admin Use:

• Added appropriate labels to PR (ex. wip, ready-for-review, docs)
• Reviewers Assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[alessio]

ACK

[jleni]

rebased, it should build correctly now

[jackzampolin]

This could also use a description of which build tags are available and what functionality is enabled by each. Maybe as a note in /docs/gaia/installation.md?

[jleni]

This could also use a description of which build tags are available and what functionality is enabled by each. Maybe as a note in /docs/gaia/installation.md?

At the moment, the Makefile does not allow passing tags. Users would have to hack the Makefile.
Nevertheless, I will document what the tags mean in the version command output.

[alessio]

@jleni dixit:

At the moment, the Makefile does not allow passing tags. Users would have to hack the Makefile.
Nevertheless, I will document what the tags mean in the version command output.

That's doable, I can deal with it.