Feature/integration testing

Issue: #31 
Utility methods & example tests have been completed, this is a good point to introduce the code to the project such that the upcoming API's can test integration aspects while in development.

**Acceptance Criteria**

- All tests exercise at least two origins-- test and IWC bus. A mock or stub origin may be necessary in some situations for coordination between participants.
  - Tests can now [generate clients] (https://github.com/ozone-development/ozp-iwc/blob/3858c46d9a0fdea331042777083afc02748a51b8/test/tests/integration/helpers/clientHelper.js#L37) to test:
    - Single client & IWC bus interaction. Ex.) [dataApiSpec.js](https://github.com/ozone-development/ozp-iwc/blob/3858c46d9a0fdea331042777083afc02748a51b8/test/tests/integration/specs/apis/dataApiSpec.js)
    - Multiple clients interacting over IWC bus. Ex.) [peerSpec.js](https://github.com/ozone-development/ozp-iwc/blob/3858c46d9a0fdea331042777083afc02748a51b8/test/tests/integration/specs/apis/peerSpec.js)
- Allow for testing of all APIs in a multi-application environment.
    - [IntegrationTestWiring](https://github.com/ozone-development/ozp-iwc/blob/3858c46d9a0fdea331042777083afc02748a51b8/test/tests/integration/bus/integrationTestWiring.js#L57) Allows api specification
    - Multi-applicaiton can be tested via generating multiple clients
- Allow for testing of the LeadershipParticipant where widgets are being opened and closed.
    - IntegrationTestWiring generates a [TestParticipant](https://github.com/ozone-development/ozp-iwc/blob/3858c46d9a0fdea331042777083afc02748a51b8/test/tests/integration/bus/integrationTestWiring.js#L7) that will send Participant data back to the client if the clients packet contains `test: true`