Introduce a separate Address table

[kderme]

Description

Fixes #1333

Checklist

• Commit sequence broadly makes sense
• Commits have useful messages
• New tests are added if needed and existing tests are updated
• Any changes are noted in the changelog
• Code is formatted with fourmolu (which can be run with scripts/fourmolize.sh
• Self-reviewed the diff

Migrations

• The pr causes a breaking change of type a,b or c
• If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
• Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate
more what the migration achieves, what it cannot achieve or why a migration is not possible.

[rdlrt]

Could this table have an additional field inserted (stake_address_id)? Useful to filter used addresses contributing towards a stake.
Absence of this field would require querying tx_out table and then doing a [distinct] fetch on address_id together

[infnada]

Is this and/or should this MR also take into account collateral_tx_out?

Also, i don't know if it's possible to have an address inside collateral_tx_out without having it in tx_out.

Not really familiar with collaterals, i would say it is possible since a collateral output can be sent to any account (assumption), and at the same time a collateral must have a tx_out where to use and reference it for "a future tx_in" in the chain, so i'm a little confused :). If that's the case and we don't handle collateral_tx_out we will end up with an address table not really containing all the addresses.

[rdlrt]

@kderme - are there plans for this PR to progress to an upcoming release? would be nice to get an insight around any blockers for this one

*The updated size difference with tx_out on mainnet is 89GB vs [37GB for tx_out + 14GB for new address table]GB respectively for structure below (where address_id is against an index for seperate table where address, address_has_script, payment_cred were moved in DB leaving leftover indexes as-is):

id,tx_id,index,address,address_has_script,payment_cred,stake_address_id,value,data_hash,inline_datum_id,reference_script_id,consumed_by_tx_id

vs

id,tx_id,index,address_id,stake_address_id,value,data_hash,inline_datum_id,reference_script_id,consumed_by_tx_id