Normalization of addresses

### Description

We suspect that, since Lotus uses robust addresses and actor IDs interchangeably, we are ingesting data with both and not accounting for the fact when making queries. i.e. the "To" field in messages could appear as f0xxxx and f3xxx for the same entity but we would not be able to identify that.

Thus, we propose to normalize addresses to robust addresses where both have risk of being used interchangeably:

* Message fields

### Options

* Option 1: Normalize addresses on processing and reprocess the tables
* Option 2: Normalize addresses on processing and insert them in a new column, keeping the original information. Needs migration before re-processing.
* Option 3: Populate a table to translate addresses.

### Acceptance criteria

* Ensure ensure message addresses are resolved during ingestion.
* Trigger re-processing of messages.

### Where to begin

* Find the best way to convert an ID to a robust address
* Modify messages task to normalize addresses based on the result of the discussion