Incorporate BrowserMobProxy in production mode as part of infrastructure

[vdelendik]

[BMP intergration]

[There are two possible ways to implement it]:

1. Embedded proxy (starts in code as Java object etc)
2. Rest proxy (starts as java process and all interactions are using REST requests)

Overview:
Embedded proxy works much more faster and lots of projects were integrated with enbedded one due to the performance issues with REST.

[LIMITATIONS]

1. There is no chance to automate process of proxy configuration on device (except of script which navigates using appium, it can be implemented in future I think):
   all existence sollutions are unstable (even for Android);
2. Devices are pre-configured (proxy is configured manually);
3. Devices have no access to the i-net due to stopped proxy;
4. Possible issues in case of lots devices are configured to one host (not sure here, there is an example with ~15 proxies and it works);
5. Separate pools of devices for proxy (not)based devices: since with proxy it works a bit slower than without.

[IMPLEMENTATION]

1. Core functionality to start/stop/configure proxy (partly implemented but I'm not sure it work in latest cores, but anyway it should be re-implemented);
2. Capabilities matcher to filter devices with/without proxy (it can be done a bit later);
3. Free port resolver: to stop processes in case port is in use;
4. ...
   

[vdelendik]

feature should be available in selenium-hub 2.9+
carina 5.2.3.67+

proxy_port should be added as appium capability for each device