Add test for fixed parsing of goto.

[DemiMarie]

Also update test for changes to the table library.

[DemiMarie]

Added ~200 new test to the test runner.

[lukego]

Regression?

$ git log --oneline -1
fda2015 Add more tests to the test suite

$ ../../luajit/src/luajit test.lua
../../luajit/src/luajit: test.lua:10: module 'ctest' not found:
        no field package.preload['ctest']
        no file './ctest.lua'
        no file '/usr/local/share/luajit-2.1.0-beta2/ctest.lua'
        no file '/usr/local/share/lua/5.1/ctest.lua'
        no file '/usr/local/share/lua/5.1/ctest/init.lua'
        no file './ctest.so'
        no file '/usr/local/lib/lua/5.1/ctest.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
        [C]: in function 'require'
        test.lua:10: in main chunk
        [C]: at 0x00404a70

[sindrom91]

I don't think this is a regression. These commits add ffi tests to the runner, so you need to compile libraries from test/src. Also, make sure that your libraries are in a place where they can be found (you might need to export appropriate LUA_CPATH).

[lukego]

To me it looks like a regression because prior to these changes the instructions in test/README.md worked for me but now they do not. Excerpt:

## Running the test suite ##

To run the default test suite, run `test.lua` using the Lua interpreter you
wish to test, for example:

    $ ~/luajit-2.0/src/luajit test.lua

[sindrom91]

Oh, I see what you're saying. I didn't look at it that way. :)

[DemiMarie]

There are some tests still failing. I believe that they indicate genuine bugs in either LuaJIT or the test suite.

I fixed the instructions in README.md.