(Feat)/reenable 1559

[NazariiDenha]

1. Purpose or design rationale of this PR

Currently Scroll does not support EIP-1559 transactions, fee markets, block fields, and opcodes (BASEFEE). We want to enable this as part of the next hard fork.
https://app.asana.com/0/1202293017617135/1205896809138440/f

Testing

EIP-1559 transactions and baseFeePerGas

• Set up local network with Banach fork activated in block number 15
• During first 15 blocks it wasn't possible to send non-legacy tx and received custom error: EIP-1559 not activated
• After that network started to accept EIP-1559 txs
• For the blocks before 15 getBlockByNumber didn't return field baseFeePerGas at all
• For later blocks it started to return baseFeePerGas that changes

BASEFEE opcode

• created and deployed simple contract

contract BaseFeeChecker {
    uint256 public basefee;

    function setBaseFee() public {
        basefee = block.basefee;
    }
}

• called setBaseFee method before Banach block. It returned error (code: -32000, message: invalid opcode: BASEFEE, data: None)
• called setBaseFee method after fork activation and checked the stored value with eth_getStorageAt. The value stored in basefee variable was the same as baseFeePerGas of corresponding block

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes

[colinlyguo]

LGTM.

[lispc]

Will this be merged soon？will be helpful for circuit side integration and testing.

The base branch was changed.

[Thegaram]

London has already happened on Scroll mainnet and Scroll Sepolia (meaning that IsLondon is already true). So changing this here would be a breaking change, it would change the state transition function, and lead to l2geth not being able to sync the chain.

[Thegaram]

I think the safest approach is to leave IsLondon everywhere and change the logic to IsBanach where there was BaseFeeEnabled. I'll push some changes.

[Thegaram]

Closing for #634.