change: ETCM-12220 Support tx-out.value = "consumed" Db-Sync option

[AmbientTea]

Description

• Adds db-sync queries that use the consumed_by_tx_id column in tx_out instead of joins with tx_in table. This column is populated when tx-out.value in db-sync config is set to "consumed"
• Adds enum TxInConfiguration { Legacy, Consumed } which signifies which set of queries should be used.
• All data sources that use queries that touch transaction inputs now select the query to use based on their configured TxInConfiguration
• TxInConfiguration value is determined by checking whether tx_in table exists and is populated
• All relevant tests are run against two sets of db migrations, this is where the bulk of LOC changes in this PR come from

Checklist

• Commit sequence broadly makes sense and commits have useful messages.
• The size limit of 400 LOC isn't needlessly exceeded
• The PR refers to a JIRA ticket (if one exists)
• New tests are added if needed and existing tests are updated.
• New code is documented and existing documentation is updated.
• Relevant logging and metrics added
• Any changes are noted in the changelog.md for affected crate
• Self-reviewed the diff

[LGLO]

Adding new queries instead of replacing existing ones and making decision in runtime which to use will cost us less than all the fallout of in-place change.

[neotheprogramist]

LGTM, but what happens if insert_options.tx_output.value option is not present, do we have any idea how to handle it or such situation is impossible?

[LGLO]

Please fill changelog and docs

[AmbientTea]

Please fill changelog and docs

Added changelog. The docs are already updated.

[LGLO]

Just please fix changelog, the config field name is invalid there