IGNITE-14071: Test for messaging type auto resolve.

[nizhikov]

The Contribution Checklist

• 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 pull request body describes changes that have been made.
  The description explains WHAT and WHY was made instead of 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.
• A reviewer has been mentioned through the JIRA comments
  (see the Maintainers list)
• The pull request has been checked by the Teamcity Bot and
  the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

• How to Contribute
• Coding abbreviation rules
• Coding Guidelines
• Apache Ignite Teamcity Bot

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.

[nizhikov]

Hello, @ptupitsyn

Can you, please, take a look at my changes.
This patch enabled "register same java type" mode for messaging.

[ptupitsyn]

As discussed on the dev list, this Java type registration behavior can be only enabled when we are calling Java user code. For Compute and Services this can be determined precisely. But for Messaging we don't know whether listeners are in .NET or Java, so this is a compatibility risk.