Architectural Improvements for Asynchronous Operations

1. topic should be mapped to the service contract name, not to the rest route
2. There should be an object, invoker, for service contracts with sync and async implementation for sync or async service contracts
3. There should be a customizable mapping from service contract to topic so default topic name can be changed
4. There should be a customizable rest route for Async Bulk API so that generated path can be overriden
5. External systems should be able to sends messages directly to the queue by topic bypassing Async WebAPI layer
   1. it requires web api allows to register bulk id, and allocate for certain amount of products. The status of operation will report how many received and for how many waiting.
6. There should be a way to have queue for the service contract with status tracking and queue for service contract without status tracking
7. bug: drop foreign key on admin table => add user type, drop foreign key, upgrade script with user type admin
8. bug: topic schema coded as ServiceName:methodName is not possible to use with MassConsumer
9. bug: MySQL queue is not possible to use with Mass Consumer