Contract Creator Mapping Model

[MSilb7]

Use creation traces to build the logic for iterating up the creation tree to find the top-level deployer that we can use for quickly mapping contracts to projects.

Steps:

1. Find all contract creations (use intermediate model creation_traces #1049 creation_traces)
2. For create2+ deployments, pull the transaction sender
3. For create deployments, iterate up the tree (i.e. check the contract that created this contract) until we get to a deployer.
4. Pull in all predeploys and OVM1 contracts for OP Mainnet
5. Produce a contract <> deployer mapping table, which we can then use to join with labels.

See what we previously built in Dune: https://github.com/duneanalytics/spellbook/tree/fd8b1de206f81c050fc8f2e641a6a540be41e4e8/dbt_subprojects/daily_spellbook/models/contracts/optimism

Note: This may be a short-term method to identify the deployer. This breaks if we move to a world where users "install" contracts on their chain. In this case, we'd need a different identifier.