add skip db write flags for tables in parquet migration tranche 2 and 3

[yuunlimm]

Summary

We have categorized our tables into four tranches to manage database better writes and prioritize our parquet processing efforts. The goal is to enable skipping database writes for tables in Tranche 2 and Tranche 3 by adding appropriate flags in each processor responsible for these models.

Here is the list of tables we have: https://docs.google.com/spreadsheets/d/1gSuE27GsGKLCBLOxhlzonvHh_bzF5i1Uzx27Mf61uh0/edit?gid=0#gid=0

Tranche Categories:

Tranche 1: tables that are huge and high priority
Tranche 2: tables that are huge and low usage
Tranche 3: v1 tables to replace with v2 tables.
Tranche 4: tables to revisit.

This enables skipping db writes for tables included in Tranche 2 and 3 by adding a flag in each processor responsible for each model.

We can add table names in the deprecated_tables field in the config as needed

Revision 2

• excluded the flags for transaction_metadata_processor as clients can stop running this processor completely, and these were for analytics purposes only.

test plan

tested when CURRENT_COIN_BALANCES was added

[rtso]

Just a note: this table is on a different deprecation timeline than the other ones for the coin -> FA migration. It's fine to add the flag, but we don't want to turn it off just yet.

[yuunlimm]

we need to re-eval this table current_fungible_asset_balances with @ying-w

[yuunlimm]

we don't need this in parquet, we can delete this table. according to Ying, we can replace with fungible_asset_balances

[yuunlimm]

Will start a separate migration plan for this table with the different timeline.

[rtso]

Wait fungible_asset_balances is going to Parquet, but we need to keep current_fungible_asset_balances for now for the coin -> FA migration, which I'll deal with .

[yuunlimm]

Migration view pr for current_collection_datas and migrating current_token_pending_claims logic to v2 will be followed up in separate pr