remove CloseError

The final else case in LevelUP#close() corresponds to the status
'new', which is the state the database has after the constructor
has been called. Since we always call LevelUP#open() before
returning the database object, it's impossible for the user to
call close() while the database is in the state 'new'. Therefore
the CloseError() can never happen.
Merge pull request #70 from rvagg/feature/rm-close-error

remove CloseError
ensure iterator end & next don't conflict

Race condition possible when you have a next() executing but end() is
also called. In the main JS thread we can create a barrier to protect
against this condition.
add test-10k-times.sh script
allow one next() at a time, improve end() handling
minor style tweaks
memory leak, Persistent callback not Disposed
explicit namespaces, tighter line wrapping