Add topic description feature

[phoenix128]

This PR adds the ability to define a topic name both via \Magento\AsynchronousOperations\Model\MassSchedule::publishMass parameter and di injection.

This will avoid to expose obscure messages from the user's perspective in the Magento backend when an async task is completed.

Currently we get messages like:

While we should have something more user friendly like:

[magento-cicd2]

All committers have signed the CLA.

[magento-cicd2]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

[nuzil]

Hey, if you will be able to fix tests will be awesome :-)
Related issue:
https://github.com/magento/async-import/issues/13

[phoenix128]

That is the plan :) . I will be back on it very soon

[vkublytskyi]

Do we really have a strong reason to change method arguments list or we may delay them till the moment when we will have some code that passes this argument?

[vkublytskyi]

@phoenix128, @nuzil in #22 we already disabled PHPMD check for coupling between objects in MassSchedule. The reason was that it is not possible to implement the required functionality in a backward compatible way. Backward compatibility is more important than coupling limit.

#22 were merged to 2.3.0-release branch. As far as 2.3.0-release will be merged back to 2.3-develop static test should not fail

[vkublytskyi]

Current implementation expects that topic descriptions are provided to descriptions pool in constructor. So this would be declared in di.xml. However, topics are defined at communication.xml. It is highly desirable to have all declarations in the same place. So if we don't have strong reasons to not to do that I think we should implement a description pool that fetches descriptions from a config file.

[nuzil]

@vkublytskyi
Can you please maybe give a tip for a good location? Cause for me logical way will be define description in communication.xml
BUT we are generating communication.xml automatically based on webapi.xml, so only way currently I see or use as was proposed di.xml, or extend webapi.xml.

[nuzil]

@phoenix128 we decided to extend webapi.xml with "description" attribute and then generate communication.xml also with "description" attribute and then it can be used on those messages.

[nuzil]

Field name: "successMessage"
Message like "%s items were successfully unassigned from stock inventory" can be defined in xml.