We previously had a wrapper script that started Sentry Service up in our test environment.
This ran in to some issue with the upgrade to Sentry v1.4 due to classpath conflicts with
other components. The fix is to add sentry to /thirdparty and use Sentry's startup scripts
to actually run the service. This is also a more realistic test environment.
The actual addition of Sentry to /thirdparty is not included in this change.
Change-Id: I4c5998cde4fc900b8a34037550459265298da4c4