Created a test proving #350
Candidate elements are now set in the state vertex.

Candidate elements are set in the state vertex once the
CandidateElementExtractor has parsed the DOM. This way, you can see
which elements were fired once the crawl is down.

These elemets are CandidateElements not Eventables because if they are
not fired, they are not an Eventable (meaning a link between vertexes).
For that reason, the method `getUsedEventables()` was removed from
StateVertex. To be able to figure out which eventables were fired and
which weren't, you can retreived the edged going out of a state.

Fixes #350
Crawler checks if left domain by hostname.

Before this was done using `String.contains(x)`. However, that does not
work when in the new URL on another domain, the original domain is
passed through as a query parameter. Because the new method compares
hostnames, this cannot happen anymore.

Fixes #339
Merge pull request #359 from keheliya/master

Fixing crawljax#358
Merge pull request #356 from crawljax/fixes/350-states-have-events

State vertexes can now show their candidate elements
Merge pull request #357 from crawljax/fixes/339-crawler-escapes-domain

Crawler checks if left domain by hostname.
Fixed NPE in Test data creation
[maven-release-plugin] prepare release crawljax-3.4
[maven-release-plugin] prepare for next development iteration
Improved tests

The browser now does not open files anymore because that leads to
security issues.
Updated versions
Merge pull request #362 from crawljax/fix-tests

Fix tests & version updates
Fixes dependency conflict in PhantomJS
Merge pull request #363 from crawljax/fix/dependency-conflict

Fixes dependency conflict in PhantomJS