fix code_size in create; fix return_data for call oog

[lispc]

Description

[PR description]

Issue Link

[link issue here]

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Contents

• [item]

Rationale

[design decisions and extended information]

How Has This Been Tested?

[explanation]

---

How to fill a PR description

Please give a concise description of your PR.

The target readers could be future developers, reviewers, and auditors. By reading your description, they should easily understand the changes proposed in this pull request.

MUST: Reference the issue to resolve

Single responsability

Is RECOMMENDED to create single responsibility commits, but not mandatory.

Anyway, you MUST enumerate the changes in a unitary way, e.g.

This PR contains:
- Cleanup of xxxx, yyyy
- Changed xxxx to yyyy in order to bla bla
- Added xxxx function to ...
- Refactored ....

Design choices

RECOMMENDED to:

• What types of design choices did you face?
• What decisions you have made?
• Any valuable information that could help reviewers to think critically

[lispc]

\b run testool 1

[zkevm-circuits-bots]

Succeed to run testool:
https://circuit-release.s3.us-west-2.amazonaws.com/testool/

[lispc]

\b run testool

[silathdiir]

\b run testool 1

[zkevm-circuits-bots]

Succeed to run testool:
https://circuit-release.s3.us-west-2.amazonaws.com/testool/default.1692969160.9af5b19.html

[zkevm-circuits-bots]

Succeed to run testool:
https://circuit-release.s3.us-west-2.amazonaws.com/testool/default.1692969485.9af5b19.html