Improvements to consume and prune tx_out migrations

[kderme]

After #1416 there are some remaining issues that can improve the consumed and prune migrations. We split them in two lists.

Issues that affect users:

• Avoid running a db-sync with and then without prune-tx-out #1486
• The consumed migration happens on a single db-transaction, which is the same transaction where the consumed_by_tx_in_id column is created. This happens because otherwise there would be partial migrations that can cause problems. This migration also takes multiple hours (up to 24) and if it is interrupted it needs to be restarted from scratch. We could save progress on a new table. This requires schema changes so it needs a major bump, eg 13.2.
• Speed up the prune migration #1511
• Using cardano-db-sync --rollback-to-slot after consumed-tx-out is bugged #1597
• Remove tx_in table as redundant with consumed_by_tx_in_id #1514
• Possible issue Error for mismatch between deleted tx_in and nullified tx_out when using prune migration #1423
• Bootstrap a dbsync instance from the ledger #1534

Internal issues/tech debts:

• ExtraMigrationssimplified and renamed #1489
• Test - restarting db-sync with alternate Command line Args #1465
• Hardcoded values Remove hardcoded use of securityParam in code #1418
• Unit tests Add tests for consumed and pruned tx_out migrations #1417

[kderme]

The second bullet is no longer needed due to alternatives #1534 and #1511