Add json field to history_operations

[chowbao]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with the jira ticket associated with the PR.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated the README with the added features, breaking changes, new instructions on how to use the repository.

What

Add json field for details to history_operations

Why

Change to support stellar/stellar-etl#270

Known limitations

• Need to test in test-hubble

[sydneynotthecity]

wdyt about also adding changes to the enriched_history_operations SQL? I think Securrency still uses that table as a source.

Also do you mind sneaking in a change to disable relevant asset trades? This would snooze the data quality alerts we're getting due to the bad SCD 2 pricing table

[chowbao]

wdyt about also adding changes to the enriched_history_operations SQL? I think Securrency still uses that table as a source.

I don't think we should. I would rather them point to the new dbt eho table.

Also do you mind sneaking in a change to disable relevant asset trades? This would snooze the data quality alerts we're getting due to the bad SCD 2 pricing table

Yeah I can add that