Improve performance of Stopword lookup

Ankusa::STOPWORDS is created once and then searched for every single
word that we are classifying.

Change it from an Array with O(n) average time complexity to a Set
(Hash-Table) with O(1) average time complexity.

In tests on 1000 emails (Single threaded) the run-time was reduced
from 6.4 seconds to 2.4 seconds.
Merge pull request #6 from rurounijones/performance-increases

Improve performance of Stopword lookup
Replace check method to see if a string is numeric

The old code used the very correct Float(word) method to see if a string
was numeric. This works reliable with all sorts of edge-case data but it
is very slow.

Since we have already parsed out a lot of possibilities during word
atomisation (e.g. decimal numbers like 123.45 have already been split
into "123" and "45") we do not need this level of "dealing with edge"
case surety.

Therefore we can just do a simple regex check to see if the string is
all numerals or not.

In tests on 1000 emails (Single threaded) the run-time was reduced
from 2.4 seconds to 1.4 seconds.

Since we have traded edge-case reliability for speed we can no longer
leave this as a String class monkey-patch so move it into a method that
will only be called by Ankusa itself
Sleep before running tests

To give time for travis-CI to get the storage services up and running
sleep for 15 seconds before starting our tests

As documented at:
http://docs.travis-ci.com/user/database-setup/#MongoDB-may-not-be-immediately-accepting-connections
Merge pull request #7 from rurounijones/performance-increases

Replace check method to see if a string is numeric