* No code changes
* Documenting the current state before I introduce a change in my next
commit

* Moved logic into smaller parts that is used the generate the full href
for the OneSignal ServiceWorker.
   - No result changes.
* Simplied the else part where we check for ServiceWorkerActiveState
   - As we always want to install service worker A in all other cases.
* The benifits of this refactor will be used in the next commit

* Added a new changedServiceWorkerParams method which check if;
   - OneSignal ServiceWorker path, filename, or query params changed.
   - OneSignal ServierWorker scope changed
* This is a new check that was added to shouldInstallWorker
* A developer might change the OneSignal service worker params to take
advantage of the PR #745 "Remove ServiceWorker Page Control Requirement"
  - This way the new OneSignal SW scope can be setup while their new
  root scoped SW can be installed at the same time.

* Multiple service workers are possible with browsers, if their scopes
are different. Updated the mock to handle this.

* MockServiceWorkerContainer.getRegistration  - Added match any SW's
that are at a higher scope than the one we are querying for as they are
under it's control.
   - This was observed behavoir when testing on real browsers.