expected conditions

Wanted to just throw out a sample test case, test application (page),
and a working keyword. Interesting this works at a very basic level. See
next paths for a few functionality like

- instead of snake_case create method for using "space case"
- add check for presence of method
- add polling delay, timeout
- ...?

These were some initial sketches for the keywords and their usage. As
they are not working I have moved them out of the test suite.

- Added 100 millisecond polling to wait. Seems like a good default. Will
  need to decide on how to let users set this.
- Copied dynamic_content.html making into seperate
  expected_conditions.html test page.
- Added another sample test case

Added timeout atest

…s_1827

added timeout argument to keyword wait_for_expected_condition

Made a few changes ..
- Catch unknown expoected conditions and reopport an error. This can still be improved
  by adding a here are the known expected conditions as well as a "did you mean ..."
  type message
- Brought in parser so one can use `Element To Be Clickable` instead of
  `element_to_be_clicable`. Admittedly it seems to simple and realized an issue, of case,
  as I type this.
- Added some test cases

Hadn't realized I do force the expected condition ame to all lower case letters. So just needed
to add a test case!

Some of the expected conditions expect a locator which is a tuple
consisting of the By string [1] and the string containing the locator.
I wanted to see what this was like. I am thinking that it would be good
to somehow use the libraries locator strategy.

Needed to also add to the test page so we had a new element after a delay.

[1] https://www.selenium.dev/selenium/docs/api/py/_modules/selenium/webdriver/common/by.html#By

…word

Made unit test compatible to both Selenium v4.17.2 and above as well as
v4.16.0 and prior

The delay for the title change was 600 miliseconds while the timeout was
0.5 seconds. I suspect this gives little time for error. The 600
milisecond timeout was specifically choosen along with the other
timeouts in the expected conditions tests such that any combination of
delays would be unique. This gives us a framework to test various
combinations. So I didn't want to change that. Noting I could simply
swap the 600 millisecond test for the 900 millisecond tes .. which might
be the best bet. But for now trying to reduce the timeout to 0.3
seconds.

This may greatly increase the archive file size which we need to simplify our matrix.
But at least we should get some more insights into failing tests.