feat(config): Set SlotCalculator config with CHAIN_NAME instead of verbose values

[Evalir]

This makes it easier to configure the builder slot calculator through setting the chain name, instead of setting each slot calculator configuration variable.

Closes ENG-1372

@rswanson this will lets us load the slot calculator from the CHAIN_NAME env var.

This also updates signet dependencies because it's needed to use the latest bin-base. No behavior change is expected.

[Evalir]

• feat(config): Set SlotCalculator config with CHAIN_NAME instead of verbose values #148 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[prestwich]

This makes the builder unrunnable for any other chain. is that intentional?

[Evalir]

It's runnable for any chain that the slot calculator supports through KnownChains? Which I think we're ok with?

[prestwich]

this is a significant change to builder functionality that makes it impossible to run on custom nets. is that intentional?

[Evalir]

Yes this is intentional. We want to make the builder easier to configure. Restricting the builders to chains we have the values in constants for is one way to do so.

[Evalir]

cc @rswanson i'd like your ACK/NACK on this before we merge

[Evalir]

Alright, with the new bin-base version now having the constants is still an option, if the CHAIN_NAME env var is not present. So this doesn't require an immediate infra change, making this safe to merge as-is.