feat(textual): Value Renderers for numbers

[amaury1093]

Description

closes #12613

This PR sets up the infrastructure for value renderers as discussed in ADR-050. It's only additive, in a new package, and isn't wired up to the rest of the codebase.

It adds a new root go module tx, which has one textual subpackage for now.

Only adds implementation for:

• integers
• decimals

Sister PR:

• Implement Sign Mode Textual cosmjs#1147

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[amaury1093]

@aaronc With the new app wiring, where should this package go? Will we have a root tx/ go mod?

[aaronc]

Generally looks like the right direction. Let's switch to a more efficient Reader/Writer implementation. We may want to pre-calculate buffer sizes like the orm does

[aaronc]

Suggested change

	Format(context.Context, protoreflect.Value) ([]string, error)
	Format(context.Context, protoreflect.Value, io.Writer) error

[amaury1093]

I guess the downside is that value renderers would need to deal with \n chars all over. By keeping []string we can just do a single .Join() at the very end.

[aaronc]

Do they need to deal with new lines actually? Shouldn't that be dealt with higher up?

[amaury1093]

For when the FieldDescriptor is a message field, there'll be new lines (in a future PR).

[amaury1093]

OK I changed to io.Reader/Writer in dbe153b. I still think []string improves code readability (wrt to dealing with \n), but we can change it easily if needed.

[aaronc]

Not seeing where there's a new line issue

[amaury1093]

OK, this is R4R again, and uses the new math.LegacyDec

[amaury1093]

OK I created a new tx module, and addressed the last nits. Would love to have a final review and merge.

[codecov]

Codecov Report

Merging #12088 (0857782) into main (ef8049a) will increase coverage by 0.02%.
The diff coverage is 62.19%.

@@            Coverage Diff             @@
##             main   #12088      +/-   ##
==========================================
+ Coverage   65.32%   65.34%   +0.02%     
==========================================
  Files         689      692       +3     
  Lines       70706    70788      +82     
==========================================
+ Hits        46191    46259      +68     
- Misses      21960    21966       +6     
- Partials     2555     2563       +8     

Impacted Files	Coverage Δ
tx/textual/valuerenderer/dec.go	46.15% <46.15%> (ø)
tx/textual/valuerenderer/int.go	65.21% <65.21%> (ø)
tx/textual/valuerenderer/valuerenderer.go	72.72% <72.72%> (ø)
x/group/keeper/keeper.go	58.26% <0.00%> (-0.40%)	⬇️
x/distribution/simulation/operations.go	90.42% <0.00%> (+9.57%)	⬆️