PlyadsTable: do not require the second column to be strictly monotonic

monotonic is sufficient. thanks to [at] qilicun for the catch!
add the ALL keyword

This keyword is undocumented but seems to be widely used. (It is even
featured by an example in the Reference Manual.)
PlyadsTable: add a unit test and fix a copy-and-paste bug unearthed by it
remove dangling file opm/parser/eclipse/Utility/tests/TableTests.cpp

somehow this fell through the cracks when doing the big tables overhaul.
remove the TlmixparTable class

that's because the TLMIXPAR keyword is not a table...
Merge pull request #323 from andlaus/add_ALL

add the ALL keyword
Revert "add the ALL keyword"
Merge pull request #324 from OPM/revert-323-add_ALL

Revert "add the ALL keyword"
change the name for the generated keyword tests to make them unambigous

the problem was the ALL keyword which caused a naming conflict with
Opm::ParserItemSizeEnum::ALL. I haven't considered the possibility to
break the build by adding a keyword, so sorry for the breakage.

On a more philosophical ground I think it is a bit questionable to
auto-generate test cases at build time because they will automatically
match the keyword definition, whether this definition makes sense or
not...
add the ALL keyword

The documentation of this keyword is quite well hidden in the "Other
SUMMARY keywords" section of the Eclipse reference manual, but the
keyword itself seems to be widely used...
Merge pull request #325 from andlaus/add_ALL_v2

Add the ALL keyword (v2)
Merge pull request #322 from andlaus/non-strictly_monotonic_in_plyads

PlyadsTable: do not require the second column to be strictly monotonic