fix: Disable deprecated Flow Control & use async / await

[Robdel12]

What is this?

Turns out Protractor uses this thing called "Webdriver Flow Control" to handle test command execution. It relies on promises to know when to go to the next step in the tests.

Flow Control is deprecated (see: SeleniumHQ/selenium#2969) and will be removed. This is because packages / tests that use async / await don't quite work with Flow Control due to the difference in promise interfaces (I'm assuming native promises vs polyfills).

Protractor recommends using async / await now (https://www.protractortest.org/#/control-flow):

In the future, the control flow is being removed (see SeleniumHQ's github issue for details). To disable the control flow in your tests, you can use the SELENIUM_PROMISE_MANAGER: false config option.

Instead of the control flow, you can synchronize your commands with promise chaining or the upcoming ES7 feature async/await. See /spec/ts/ for examples of tests with the control flow disabled.

Because async/await uses native promises, it will make the Control Flow unreliable

This PR also removes the windows test commands since they're not needed anymore. 👍

[djones]

🍍 LGTM