fix: replace message-related field into JSON type from JSONB

[dadamu]

Description

This PR intends to fix the issue that message JSON may includes invalid Unicode sequence \u0000, it would cause the error when saving transactions and messages into Database.

Reference:
Invalid unicode sequence on PostgreSQL
Jackal transaction including invalid unicode sequence

Checklist

• Targeted PR against correct branch.
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Wrote unit tests.
• Re-reviewed Files changed in the Github PR explorer.

[0x7u]

Good catch 👍🏻 . It's also a good learning.

These are the trade-offs using JSON vs JSONB type:

The json and jsonb data types accept almost identical sets of values as input. The major practical difference is one of efficiency. The json data type stores an exact copy of the input text, which processing functions must reparse on each execution; while jsonb data is stored in a decomposed binary format that makes it slightly slower to input due to added conversion overhead, but significantly faster to process, since no reparsing is needed. jsonb also supports indexing, which can be a significant advantage.

https://www.postgresql.org/docs/current/datatype-json.html#:~:text=The%20json%20data%20type%20stores,since%20no%20reparsing%20is%20needed.

We are not indexing this column? (I believe we are not, just want to make sure)

[dadamu]

@0x7u We didn't index on JSONB column, to make sure the data is exactly the same as blockchain shows, we should allow \u0000 input used by chains, especially Jackal.

About trading-off the performance, the document said JSONB has better performance on processing, but we don't use any function and indexing to process on it, therefore it is safe to migrate JSONB to JSON.