This reverts commit 9e325636.

Dan f/upgrade travis mongo

TNL-604

Use group_id if present when getting user thread and comment counts.

TNL-543

upgrading newrelic

Add the ability to query multiple group ids

Added thread type attribute.

Add validation for undo_vote_for to avoid a crash

Add group_id to payload from notifications.

TNL-299

Filter commentable queries by course_id

Bug: TNL-207

Allow filtering by group_id in more endpoints

Number of post are incorrect

Number of post are incorrect becuase deletion of comments doesn't perform deletion of subcomments one by one which cause magical comment counter not to decrese the counter properly
TNL-91

All endpoints that return lists of threads (except the endpoint used by
the notifier component) now allow filtering by group_id and are tested
accordingly.

Make Travis use an ES version we support

Add/update thread filters (flagged, unread, unanswered).

Add thread type feature

There are two thread types, discussion and question. Discussions have
the same behavior that current threads do. When a question is returned
from the API, it contains separate fields for its endorsed and non-
endorsed entries.

Co-authored-by: Jim Abramson <jsa@edx.org>

Editing a comment such that it matched a blocked hash would cause the
API to return 503 but actually update the comment. This is now fixed.

Refactor search, fix a bug, and implement spelling correction

If a search has no results, then we will get suggestions from
Elasticsearch, re-query with the top suggestion, and return the results
from that query along with the suggestion that was used.

This change also changes search so that a document must match all terms
to be included in the results instead of any term.

This contains several improvements and bug-fixes:

* Take advantage of indexing changes in ead2f5e3 to reduce the number of
  round trips to execute a search
* Use Tire scan to include all matching threads
* Execute final sort/pagination in Mongo
* Share sorting code
* Eliminate separate presenter for search results (which removes unused
  highlighting functionality)

JIRA: FOR-607

use a single index in elasticsearch for both document types.

WARNING: Must rebuild search index!

Starting with this change, the name of the search index used by the
service has changed.  The new search index must be created before
deploying this version of the application.  There are two ways of doing
this:

* Offline (recommended)
Follow [these instructions](https://github.com/edx/cs_comments_service/wiki/Search-Indexes#offline-procedure) to perform an offline rebuild.

* Online
1. Deploy this code to a host which is not serving HTTP requests, and
run `rake search:rebuild`
2. When the rebuild finishes, deploy the updated code on live servers.
3. run `rake search:catchup[MINUTES]` where minutes is the amount of
time it took to run rebuild in step 1.
4. run `rake search:prune`

Fix task seed in Rakefile