Reduced the number of channels between service and process (#1)

[ysingh7]

• Reduced the number of channels between service and process

• Fixed the bug with failing monitor cases

Issue Number: Remove hacks and refactor Runtime and RuntimeService/Synchronizer #86

Objective of pull request: Reduced the number of channels between service and process

Pull request checklist

Your PR fulfills the following requirements:

• [X ] Issue created that explains the change and why it's needed
• Tests are part of the PR (for bug fixes / features)
• Docs reviewed and added / updated if needed (for bug fixes / features)
• [X ] PR conforms to Coding Conventions
• PR applys BSD 3-clause or LGPL2.1+ Licenses to all code files
• Lint (pyb) passes locally
• Build tests (pyb -E unit) or (python -m unittest) passes locally

Pull request type

Please check your PR type:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• [X ] Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation changes
• Other (please describe):

What is the current behavior?

• Currently we have five channels between runtime service and process model.
• 1. Used for sending cmd from RS to PM
• 2. Used for sending ack back from PM to RS
• 3. Used for sending READ/WRITE Req from RS to PM
• 4. Used to send write data from RS to PM
• 5. Used to send read data from PM to RS

What is the new behavior?

• Reduces the number of channels between runtime service and process model. Also it removes the notion of time step from the runtime.
• 1. One way channel for all cmd/get-set-req/data from RS to PM
• 2. One channel for all ack/data from PM to RS

Does this introduce a breaking change?

• Yes
• No

Supplemental information