IGNITE-22560 Processing messages to yourself in a thread pool

[tkalkirill]

https://issues.apache.org/jira/browse/IGNITE-22560

Thank you for submitting the pull request.

To streamline the review process of the patch and ensure better code quality we ask both an author and a reviewer to verify the following:

The Review Checklist

• [ ] Formal criteria: TC status, codestyle, mandatory documentation. Also make sure to complete the following:
  - There is a single JIRA ticket related to the pull request.
  - The web-link to the pull request is attached to the JIRA ticket.
  - The JIRA ticket has the Patch Available state.
  - The description of the JIRA ticket explains WHAT was made, WHY and HOW.
  - The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
• [ ] Design: new code conforms with the design principles of the components it is added to.
• [ ] Patch quality: patch cannot be split into smaller pieces, its size must be reasonable.
• [ ] Code quality: code is clean and readable, necessary developer documentation is added if needed.
• [ ] Tests code quality: test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources.

Notes

• Apache Ignite Coding Guidelines

[rpuch]

This will worsen latency, especially for embedded scenarios. Are we sure we want to trade latency to throughput this way? I mean, earlier a lot of work was done to stay in the same thread whenever possible, but now we are going in the opposite direction.