Add TestingBot DriverProvider

[testingbot]

This commit adds TestingBot as a driverProvider.

The provider will send the testingbotKey and testingbotSecret config values to the TestingBot grid.
When the test has finished, the test success state is sent to TestingBot and a link to view the test is provided.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[testingbot]

I signed it!

[googlebot]

CLAs look good, thanks!

[googlebot]

CLAs look good, thanks!

[testingbot]

Hi,

If there's any change that needs to be made - please let me know.

Thanks!

[juliemr]

Hey folks, sorry for the slow response here. We're working on a big update of our selenium dependencies and moving to TypeScript for the next release - we'll be able to take a look at this after that one's out the door.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

[testingbot]

@juliemr please let me know when it's a good time to merge this, we will probably need to change some things in this PR for things to work with your selenium dependencies update?

[testingbot]

Hi,

We'll probably need to re-create this pull request. Is this big update finished which @juliemr mentioned on April 22 (see message in this thread)?
If so, we'll recreate the pull request

[sjelin]

Hey @testingbot, yeah, sorry again for being so slow. The big update is done though