Added a test ensuring that new driver methods are added to the CoreDriver

This test is written in a way ensuring that we get a nice failure and not a fatal error (the faster way to ensure the implementation of method would be to instantiate a child class of CoreDriver, but it would not be user-friendly).

I also moved the ``@throws UnsupportedDriverActionException`` to the interface as it is the right place to say that the exception should be thrown when the action is unsupported