[Bug]: star lark stored procedure transaction scope is not clearly understood

### Is there an existing issue for the same bug?

- [x] I have checked the existing issues.

### Branch Name

main

### Commit ID

6873bd3

### Other Environment Information

```Markdown
- Hardware parameters:
- OS type:
- Others:
```

### Actual Behavior

stored procedure may begin/commit transaction at random places, not clear if we got everything right.

### Expected Behavior

Should have a well defined behavior. For example,

Top level CALL should start a transaction by its own. If there is an existing open transaction.
If a stored procedure execute mo.sql('CALL ...'). inside a stored procedure, it should keep using the transaction that is opened at top level.

### Steps to Reproduce

```Markdown
bvt
```

### Additional information

_No response_