Hiding 'low-value' 'test' annotations from the client

**Issue:**
In an effort to improve the relevance and quality of our content it is proposed that we investigate and implement a solution to hide the plethora of annotations that feature only the word 'test'.

Below is a comment made by @robertknight and @lyzadanger with respect to this issue:

@robertknight: To answer your Q @dawa we don’t have any automated filtering of annotations in the public channel for “usefulness” or “non-TEST-iness”.

My current gut feeling is that right than out-right deleting these, since they are not abusive, we probably ought to apply some server or client-side filtering to hide “low value” annotations from the default view but enable them to be fetched if the user really wants to see them. Perhaps we could auto delete annotations that we are confident are very-low value after some time period has elapsed.

@lyzadanger: I’d tend to lean toward “keep and hide”.

Creating this issue as a placeholder.

**Justification:**
Implementing this will also reduce the potential 'moderation' load, improve relevance, and as a selling point for our partners and end users that we have a way to reduce extraneous content and improve the quality of annotations across the board.

The issue names no files, tests, or entry points. Start by clarifying whether filtering belongs on the server or client and how hidden annotations remain fetchable. Done requires an agreed implementation scope for hiding annotations that contain only “test”.

Written by the indexing model from the issue text.