fix(trace): fix memory trace size

[lispc]

1. Purpose or design rationale of this PR

pick ethereum#24867 from upstream.
this pr fixes memory size in trace

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

[HAOYUatHZ]

if operation.memorySize != nil is also inside if operation.dynamicGas != nil in https://github.com/holiman/go-ethereum/blob/97f308a98f9f2f557a0815665f6497eac8f469fd/core/vm/interpreter.go#L207-L217

should we sync it?

[lispc]

if operation.memorySize != nil is also inside if operation.dynamicGas != nil in https://github.com/holiman/go-ethereum/blob/97f308a98f9f2f557a0815665f6497eac8f469fd/core/vm/interpreter.go#L207-L217

should we sync it?

seems a standalone performance optimization pr. ethereum#24048.

So at least in this pr we will not pick that