deps!: bumping nmt to v0.19.0, breaking rpc response fields

[distractedm1nd]

Related: #2633

[Wondertan]

Changes of the name do not break protos. Changes of the type and fields reorder do.

[codecov-commenter]

Codecov Report

Merging #2643 (97a3881) into main (47047f3) will decrease coverage by 0.28%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2643      +/-   ##
==========================================
- Coverage   51.34%   51.06%   -0.28%     
==========================================
  Files         158      158              
  Lines       10559    10559              
==========================================
- Hits         5421     5392      -29     
- Misses       4669     4693      +24     
- Partials      469      474       +5     

see 7 files with indirect coverage changes

[distractedm1nd]

@Wondertan, interesting, assumed it is breaking since older versions will use different names? Or does the way it work not care about naming and just uses data types and offsets. The JSON representation is definitely breaking, it is at least breaking our RPC return types that embed nmt.Proof

[Wondertan]

Or does the way it work not care about naming and just uses data types and offsets.

Yes

[renaynay]

Can we bump when we bump core?

[distractedm1nd]

sure, but then we should mark the core bump as breaking, since it breaks rpc response types

[distractedm1nd]

closing in favor of core bump #2646