refactor: Implement driver-specific W3C option classes

[mykola-mokhnach]

Change list

MobileOptions is too generic. We need something specific for each driver. Also, there should be a possibility to "share" specific capabilities between option classes, which is implemented using default interface methods. Chaining is still supported properly.

Types of changes

What types of changes are you proposing/introducing to Java client?
Put an x in the boxes that apply

• No changes in production code.
• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)