feat: add support for binary_mappings and network_family configs

[popzxc]

Motivation

Fixes #9227

This PR makes it possible to use foundry profiles to redirect execution to alternative foundry implementations (e.g. forge to forge-zksync or anvil to anvil-zksync) in an extendible way.

Solution

We introduce two new configuration options:

• binary_mappings: this setting allows you to specify where the execution should be redirected to. In essense, it's a map from enum with keys ["anvil", "cast", "chisel", "forge"] to arbitrary paths.
• network_family: an enum which currently has two options (ethereum and zksync) that allows overriding default configuration. Right now the only thing it does is override binary_mappings to ZKsync-specific values.

In combination, it makes it possible to define a profile for zksync, e.g.:

[profile.zksync]
network_family = "zksync"

and it would redirect commands to the foundry-zksync.

This way there is no need for foundry-zksync to override foundry binaries, as well as there is no need for users to change their scripts if they work with both upstream foundry and zksync foundry (which they would have to if we named binaries differently).