Bug: Method call within a method callback handler not possible

### Description

Scenario is as follows:
1. App1 offers interface Foo with method FooMethod
2. App2 offers interface Bar with method BarMethod.

App1 calls BarMethod and BarMethod calls FooMethod from within the method callback handler.
```
App1 (Foo) App2 (Bar)
| |
| -------- 1. BarMethod() -------------> |
| |
| | - Processing BarMethod
| |
| <------- 2. FooMethod() -------------- |
| |

- Processing FooMethod |
| |
| ------- 3. FooMethod returns --------> |
| |
| |
| <------ 4. BarMethod returns --------- |
| |
| |

```
The processing of Foo method returns an error.

`MessagePassingService: Sending CallServiceMethodMessage to node_id 618520 failed with error: An OS error has occurred with error code:
Local failure has been detected by the binding. `

### Error Occurrence Rate

None

### How to reproduce

_No response_

### Supporting Information

_No response_

### Classification

minor

### Affected Version

0.5

### Expected Closure Version

0.5

### Category

- [ ] Safety Related
- [ ] Security Related

Start by tracing the MessagePassingService path that sends CallServiceMethodMessage, focusing on the nested FooMethod call made from the BarMethod callback. Reproduce the App1/App2 sequence described and identify why the callback returns the binding OS error; done means the nested call and both method returns complete successfully.

Written by the indexing model from the issue text.