Bugfix/ls24004538/nested call error stack

[dom-apuliasoft]

Description

Note: This PR does not introduce/fix any RPGLE functionality but rather fixes a regression introduced in a precedent PR.

Fix a regression introduced with changes in #644 that caused errors thrown deeply in the program stack to not cleanup the stack state similarly to what we had in #642.

Related to:

• LS24004538
• Bugfix/ls24004538/call error indicator program stack #642
• Move error handling logic to CallStmt #644

Checklist:

• If this feature involves RPGLE fixes or improvements, they are well-described in the summary.
• There are tests for this feature.
• RPGLE code used for tests is easily understandable and includes comments that clarify the purpose of this feature.
• The code follows Kotlin conventions (run ./gradlew ktlintCheck).
• The code passes all tests (run ./gradlew check).
• Relevant documentation is included in the docs directory.

[lanarimarco]

I might have missed a structural problem.
I would suggest focusing on:

• Removing push and pop in the RpgProgram.execute implementation
• Including them only in CallStmt.execute and ProgramInterpreter.execute

[dom-apuliasoft]

I moved the stack managing logic in two places:

• When we execute a RpgProgram directly (for instance the root program)
• When we call an RpgProgram (push occurs after checking program is valid, pop occurs when the execution ends or when we quit call statement with an error indicator)

Therefore I am unmarking this for draft state for further review.