Rename L1ChainID to ChainID in Config to Avoid Ambiguity in L1/L2 Transaction Handling

[rachit77]

Description:

Since the tx-manager handles both L1 and L2 transactions, the current field name L1ChainID can be misleading. To make it more intuitive, it should be renamed to ChainID.

// Config represents the configuration of the etherman
type Config struct {
	// URL is the URL of the Ethereum node for L1
	URL string `mapstructure:"URL"`

	// allow that L1 gas price calculation use multiples sources
	MultiGasProvider bool `mapstructure:"MultiGasProvider"`
	// Configuration for use Etherscan as used as gas provider, basically it needs the API-KEY
	Etherscan etherscan.Config
	// L1ChainID is the chain ID of the L1
	L1ChainID uint64 `mapstructure:"L1ChainID"`
	// HTTPHeaders are the headers to be used in the HTTP requests
	HTTPHeaders map[string]string `mapstructure:"HTTPHeaders"`
}

reference

By renaming it to ChainID, the purpose of the field becomes clearer in the context of both L1 and L2 transactions.