ChromeDriver binary capability is not propagated

Due to double deprecation checks, something a capability might get lost.

For instance:

• configuration contains chromeBinary field
• capability is named chrome.binary

Hence, when this is set, double deprecation message is emitted but capability is actually never put to map but field is set instead. Factory does not rely on deprecated field, expecting that legacy configurator did the work and value is effectively lost.