Deploy scraper with Sealevel chains like Solana / Eclipse

[tkporter]

blocked by: https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4273

• At this point we expect e2e coverage on Sealevel scraping
• Now let's actually run it in the wild

Rolling this out probably should involves similar steps as what's described here when rolling out Cosmos: https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3356. maybe even at the same time?

We'll want to be cautious about this breaking prod services that depend on the scraper, e.g. the explorer UI, because this involves a DB schema change (e.g. https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3331). Instead of rolling this out straight to prod on the existing scraper, I think it may be better to deploy this new scraper alongside the old one, with the intent of eventually shutting down the old scraper and moving over to this new one. This way we'll continue to have the explorer UI work well & give Rossy / others the opportunity to move over to this new DB. If we've already spun up a new scraper that works with Cosmos chains that isn't yet consumed by any services, we can just ship to that one, being cautious of any DB incompatibilities. Imo it's easier to avoid a data migration and just sync from scratch, but defer to whoever does this