Support specifying chain ID

[mikiw]

Usage related changes

• User can specify --chain_id argument as "MAINNET" or "TESTNET"

Development related changes

• DEFAULT_GENERAL_CONFIG is now assignet to build_devnet_general_config() function in tests.

Checklist:

• Applied formatting - ./scripts/format.sh
• No linter errors - ./scripts/lint.sh
• Performed code self-review
• Rebased to the last commit of the target branch (or merged it into my branch)
• Documented the changes
• Linked the issues which this PR resolves
• Updated the tests
• All tests are passing

[mikiw]

Just thinking that maybe adding a test for it would be nice but I'm not sure how to verify this chain id in the test.

I'll try to find out.

[FabijanC]

The Updated the tests checkbox shouldn't be checked if no tests were introduced.

I would recommend testing an illegal value (see test_fork_cli.py for reference).

A way to test if MAINNET chain ID is set up correctly is to assert that transactions signed using chain_id=TESTNET fail. Notice that in test/account.py::_get_transaction_hash we have StarknetChainId.TESTNET hardcoded - it should be made configurable. It should be asserted that a tx is accepted when the correct chain id is used for signing.