fix(api): use overridden chainConfig in standardTraceBlockToFile

[0xmountaintop]

1. Purpose or design rationale of this PR

chainCfg has been overridden, we should use the overridden one.

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

[Thegaram]

It looks like the only override that we might apply is BerlinBlock, is that intended?

[0xmountaintop]

1. that's the only one override i find in this file
2. the override code (L733~734) is from 3-year-ago upstream, not made by us.
3. in L770, the original code uses chainConfig, but L772 is introduced by use and it's using api.backend.ChainConfig()

[Thegaram]

Should we make it more generic? https://github.com/ethereum/go-ethereum/blob/master/eth/tracers/api.go#L761-L769 Or is that a lot of extra work?

[0xmountaintop]

yes on "upstream" branch it's more generic, we can also update here on develop branch. I can update.

[Thegaram]

Closing as stale.