This was mostly meant to be used by the Browser Content Toolbox
which has been recently removed.
We should no spawn a commands which is focusing only on a given content process.
Instead a main process commands should be used and targets will be exposed for each content process.
Differential Revision: https://phabricator.services.mozilla.com/D166076
Tests that were using `evaluateJSAsync` are updated, either by using the new command,
or by awaiting for the `evaluationResult` event.
A couple chrome tests were moved to devtools/shared/commands/js/tests/ and turned
into browser tests, and some of them were completely removed as we tested the
features in mochitests as well.
Differential Revision: https://phabricator.services.mozilla.com/D116248
Mark Banner