json-schema-validator also uses the suite

Heck, most data in it came fom this project's test files to begin with!
json-schema-validator also uses the suite

Heck, most data in it came fom this project's test files to begin with!
Move "1.0 is not an integer" to the optional tests section

Thanks to some brain damaged languages, and given what section 5.5 says, this
test has to go in this section.

What on earth was ECMA thinking, I wonder.

Solves issue #22.
Fix syntax error in newly created test
Rename "1.0 is not int" test to a more meaningful name

I am overreacting on such matters.

See issue #22.
Changed ridiculous test description.
patternProperties: check regex engine matching more completely

* Regex matches are not anchored.
* Matching is case insensitive.
bignum.json: add a real number test

The only test was to recognize a number as an integer. Add a test to check a
mathematical operation on such a numer. And take a float.
Add corner case tests for ECMA 262 regexes

Add a very bizarre construct which only ECMA 262 allows in regexes. Check that
lookbehinds are _not_ supported.
Merge branch 'master' into develop
Merge pull request #24 from fge/master

Resubmitting...
Merge branch 'master' into develop
Transfer draft3 tests which need no changes for draft4
Update required test for draft4
Update type test for draft4
Copy maximum test from draft3 to draft4
Convert divisibleBy test to multipleOf for draft4
Convert 'disallow' test to 'not' test for draft4
Convert 'extents' test to 'allOf' test for draft4
Convert 'edpendencies' test for draft4
Add another test to dependencies