bug 1533831: remote: remove browser.fission.simulate pref; r=ochameau,yulia

The browser.fission.simulate preference has been split
into two preferences: fission.frontend.simulate-events and
fission.frontend.simulate-messages.

The remote agent briefly used the child actor system from the
Firefox frontend code when we prototyped the initial remote agent,
but it no longer relies on it.  This means we can drop the reference
to browser.fission.simulate altogether.

DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D27538

--HG--
extra : moz-landing-system : lando

remote/README

@@ -20,4 +20,4 @@ build it, put this in your mozconfig:
 This exposes a --remote-debugger flag you can use to start the
 remote agent:
 
-	% ./mach run --setpref "browser.fission.simulate=true" -- --remote-debugger
+	% ./mach run --remote-debugger

remote/doc/Building.md

@@ -9,7 +9,7 @@ To build it, put this in your [mozconfig]:
 This exposes a `--remote-debugger` flag you can use to start the
 remote agent:
 
-	% ./mach run --setpref "browser.fission.simulate=true" -- --remote-debugger
+	% ./mach run --remote-debugger
 
 When you make changes to the XPCOM component you need to rebuild
 in order for the changes to take effect.  The most efficient way to

remote/doc/Debugging.md

@@ -9,6 +9,6 @@ To increase the internal logging verbosity you can use the
 
 If you use mach to start the Firefox:
 
-	./mach run --setpref "browser.fission.simulate=true" --setpref "remote.log.level=Debug" -- --remote-debugger
+	./mach run --setpref "remote.log.level=Debug" --remote-debugger
 
 [preference]: ./Prefs.md