[Review Only] Landing CDT-independent livedev implementation

Brings in new Live Preview implementation incubated at njx/brackets-livedev2 which allows running on multiple browsers (more details on the internals at ```README.md```). The new implementation can be used as a swap-in replacement of the current ```LiveDevelopment``` implementation. 

Set ```livedev.multibrowser``` preference to true in order to make it work. If enabled, it will launch the page in your default browser when clicking on the Live Preview icon as it works today. You should then also be able to copy and paste the URL from that browser into any other browser, live edits will then update all connected browsers at once.

Main assets will land under ```LiveDevelopment/MultiBrowserImpl``` while the main module ```LiveDevMultiBrowser``` (equivalent to ```LiveDevelopment```) will land under ```LiveDevelopment``` folder. This is probably not the more elegant choice but the decision mainly relies on these two needs:

 * Keep current modules from ```LiveDevelopment``` without moving them from the original place since many extensions require them as dependencies
 * Keep multi-browser implementation under this folder since it is an (still experimental) implementation of ```LiveDevelopment```.

Changes included in ```LiveDevelopment/main.js``` allows managing both implementations. Both modules are loaded and initialized. A listener for preference changes is in charge of setting the active implementation based on pref value. Current implementation will be active and work as today by default.

There are still key things to do (launchers for particular browsers, UX/UI, multi-host support, unit/integration tests that run on different browsers, among others). Some of them will also need some previous discussion but, it is important to get this implementation landed in core so we can get some feedback from developers and also submit PRs that allows evolving it including changes that could potentially impact some areas of the underlying infrastructure.
Instead of `livedev.multibrowser` preference being a `boolean`, what do you think about making it an Object?

It would have to define:
* path to module
* status tooltip array
* status style array

This way, anyone could define their own Live Preview implementation. All of the LiveDevMultiBrowser code could stay as an default/extension to illustrate how to add new implementations.