Element Click: no need to check enabled state

It's completely legit to click on an element that is not
enabled. Pointless, but still acceptable. The existing
Selenium implementations (based on the atoms) do not bother
with checking this state, so it seems unnecessary for
implementations of this spec to do so.

Author: shs96c

webdriver-spec.html

@@ -5229,8 +5229,6 @@ <h3>Element Click</h3>
   is <a>obscured</a> by another <a>element</a>,
   return <a>error</a> with <a>error code</a> <a>element click intercepted</a>.
 
- <li><p class=issue>Check if element is enabled.
-
  <li><p>Matching on <var>element</var>:
 
   <dl class=switch>